CVE-2026-81926

MEDIUMNVD 6.16.1—
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory (severity: LOW) published 2026-09-15. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

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

Concrete CMS 9.4.0 through 9.5.2 did not escape colliding page paths before rendering them in the location panel's duplicate-path confirmation dialog. The panel's check endpoint returned the submitted path unmodified in its JSON response, and client-side JavaScript inserted each value into the dialog as raw HTML, so a crafted page path executed script in the editor's authenticated browser session. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.0 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks Yonatan Drori from Tenzai for reporting.

CVSS v3
6.1
EG Score
6.1(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 21, 2026

References (1)

Vendor Advisories for CVE-2026-81926(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-24 15:59 UTCEG score recompute
  2. 2026-09-24 15:59 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 16:37 UTCGHSA enrichment
  6. 2026-09-22 17:16 UTCEG score recompute
  7. 2026-09-22 17:16 UTCGHSA enrichment
  8. 2026-09-22 16:01 UTCEPSS rescore
  9. 2026-09-21 21:09 UTCEPSS rescore
  10. 2026-09-21 17:55 UTCEG score recompute▲ 4.10
  11. 2026-09-21 17:55 UTCGHSA enrichment
  12. 2026-09-21 17:55 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-20 01:12 UTCEG score recompute
  15. 2026-09-20 01:12 UTCGHSA enrichment
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-16 19:26 UTCGHSA enrichment
  18. 2026-09-16 18:27 UTCEG score recompute
  19. 2026-09-16 18:26 UTCGHSA enrichment
  20. 2026-09-16 18:00 UTCEG score recompute
  21. 2026-09-16 18:00 UTCGHSA enrichment
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-15 21:20 UTCEG score recompute
  24. 2026-09-15 20:28 UTCEG score recompute
  25. 2026-09-15 20:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81926?
CVE-2026-81926 is a medium vulnerability published on September 15, 2026. Concrete CMS 9.4.0 through 9.5.2 did not escape colliding page paths before rendering them in the location panel's duplicate-path confirmation dialog. The panel's check endpoint returned the submitted path unmodified in its JSON response, and client-side JavaScript inserted each value into the…
When was CVE-2026-81926 disclosed?
CVE-2026-81926 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81926 actively exploited?
CVE-2026-81926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.7% of all scored CVEs.
What is the CVSS score of CVE-2026-81926?
CVE-2026-81926 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-81926?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81926, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81926?

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

Book a Demo →Browse All CVEs