CVE-2026-107377

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-08. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-95134 (ENISA EUVD) · GHSA-77xj-x4rm-935c (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

datamodel-code-generator generates Python data models from schema definitions. From 0.59.0 until 0.81.0, an attacker-controlled Protobuf schema can supply absolute or parent-directory paths captured by WEAK_IMPORT_PATTERN and consumed by _write_missing_weak_imports in src/datamodel_code_generator/parser/protobuf.py. Exploitation requires a victim or automated job to process the attacker-controlled schema with Protobuf input support, which requires the grpcio-tools package. The paths escape the weak_imports temporary directory before protoc runs, allowing creation of directory trees and new files or overwrite of existing writable files with a generated Protobuf syntax declaration. The effect persists when later Protobuf compilation fails. The written content is limited to a proto2 or proto3 syntax declaration, and direct arbitrary code execution has not been demonstrated. This issue is fixed in version 0.81.0.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 8, 2026

Last Modified

October 14, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub release Patch Available

0.81.0

Patch available: datamodel-code-generator/datamodel-code-generator 0.81.0

https://github.com/datamodel-code-generator/datamodel-code-generator/releases/tag/0.81.0
GitHub commit Patch Available

commit 5e94b8f42031 (datamodel-code-generator/datamodel-code-generator)

Patch available: datamodel-code-generator/datamodel-code-generator 0.81.0 (contains commit 5e94b8f42031)

https://github.com/datamodel-code-generator/datamodel-code-generator/commit/5e94b8f4203198798ec66b8e48217f70af69a0dc
GitHub advisoryMentions a patch (unverified)

Protobuf weak-import path traversal allows files to be written outside the temporary directory · Advisory · datamodel-code-generator/datamodel-code-generator · GitHub

https://github.com/datamodel-code-generator/datamodel-code-generator/security/advisories/GHSA-77xj-x4rm-935c

Vendor Advisories for CVE-2026-107377(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdatamodel-code-generator @ 0.81.0 (fixes >= 0.59.0, <= 0.80.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
datamodel-code-generator0.59.0 ... 0.80.0 (38 versions)
  • 0.59.0 up to 0.81.0: fixed in 0.81.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-77xj-x4rm-935c · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-10-27 19:41 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-25 14:54 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-20 19:12 UTCEG score recompute
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-18 05:07 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 17 more
  1. 2026-10-14 02:26 UTCEG score recompute
  2. 2026-10-14 01:37 UTCEG score recompute
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  4. 2026-10-12 16:38 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  6. 2026-10-11 20:14 UTCEG score recompute
  7. 2026-10-11 18:26 UTCEG score recompute
  8. 2026-10-11 15:00 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  10. 2026-10-11 12:12 UTCEG score recompute
  11. 2026-10-11 01:16 UTCEG score recompute
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-10 03:22 UTCEG score recompute
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-08 18:36 UTCEG score recompute
  16. 2026-10-08 17:59 UTCEG score recomputeFirst assessed: 7.5 HIGH
  17. 2026-10-08 17:59 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107377?
CVE-2026-107377 is a high-severity vulnerability; its CVE record was published on October 8, 2026. datamodel-code-generator generates Python data models from schema definitions. From 0.59.0 until 0.81.0, an attacker-controlled Protobuf schema can supply absolute or parent-directory paths captured by WEAK_IMPORT_PATTERN and consumed by _write_missing_weak_imports in…
When was the CVE record for CVE-2026-107377 published?
The CVE record for CVE-2026-107377 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-107377 actively exploited?
CVE-2026-107377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107377?
CVE-2026-107377 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107377?
A fix for CVE-2026-107377 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107377 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107377

Explore →

Is Your Infrastructure Affected by CVE-2026-107377?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs