CVE-2026-112026

LOWPre-NVD 3.73.7
EchelonGraph scoreHIGH confidence

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

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

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

Also known asEUVD-2026-104007 (ENISA EUVD) · GHSA-gfvm-xrcv-wj4c (GitHub Security Advisories)Source: ENISA EUVD

3.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.2%CVSS: 3.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A security vulnerability has been detected in light0011 cms c774dce31c6df0055568a8d5c53d964d99be199d/f72cf46f601efb2a0618c3814cc2f61380b38930. Affected is the function sha1 of the file App/Home/Model/UserModel.class.php. The manipulation of the argument Password leads to password hash with insufficient computational effort. The attack may be initiated remotely. A high degree of complexity is needed for the attack. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
3.7
EG Score
3.7LOWhigh confidence
EG Risk
33
EG Risk 33/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)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
10th
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 (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 18, 2026

Last Modified

October 22, 2026

References (6)

Vendor Advisories for CVE-2026-112026(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 26× 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-10-29 18:19 UTCEG score recompute
  2. 2026-10-29 18:19 UTCGHSA enrichmentGHSA-gfvm-xrcv-wj4c · GitHub severity LOW · GitHub CVSS 3.7
  3. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-29 14:55 UTCOSV refresh
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-25 14:51 UTCEG score recompute
  10. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-22 03:26 UTCEG score recompute
  14. 2026-10-22 03:26 UTCGHSA enrichmentGHSA-gfvm-xrcv-wj4c · GitHub severity LOW · GitHub CVSS 3.7
  15. 2026-10-22 03:25 UTCNVD updateCVSS v4 → 2.9
  16. 2026-10-22 02:37 UTCEG score recompute
  17. 2026-10-22 02:36 UTCGHSA enrichmentGHSA-gfvm-xrcv-wj4c · GitHub severity LOW · GitHub CVSS 3.7
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-19 15:28 UTCEG score recompute
  22. 2026-10-19 15:27 UTCGHSA enrichmentGHSA-gfvm-xrcv-wj4c · GitHub severity LOW · GitHub CVSS 3.7
  23. 2026-10-18 23:26 UTCEG score recompute
  24. 2026-10-18 23:25 UTCNVD updateCVSS v4 → 2.9
  25. 2026-10-18 22:26 UTCEG score recomputeFirst assessed: 3.7 LOW
Show 1 more
  1. 2026-10-18 22:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-112026?
CVE-2026-112026 is a low-severity vulnerability; its CVE record was published on October 18, 2026. A security vulnerability has been detected in light0011 cms c774dce31c6df0055568a8d5c53d964d99be199d/f72cf46f601efb2a0618c3814cc2f61380b38930. Affected is the function sha1 of the file App/Home/Model/UserModel.class.php. The manipulation of the argument Password leads to password hash with…
When was the CVE record for CVE-2026-112026 published?
The CVE record for CVE-2026-112026 was published on October 18, 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-112026 actively exploited?
CVE-2026-112026 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112026?
CVE-2026-112026 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112026?
No fix for CVE-2026-112026 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-112026 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-112026

Explore →

Is Your Infrastructure Affected by CVE-2026-112026?

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

Book a Demo →Browse All CVEs