CVE-2026-82380

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Cross-Site Request Forgery (CSRF) in Apache Roller 6.1.5 allows a remote attacker to cause a logged-in user to perform state-changing actions under the victim's authority, because the CSRF validation filters accept a request that does not submit the required salt token, validating instead against a value the server itself generated for the request. No optional feature or non-default configuration is required; any logged-in author or administrator is affected when induced to visit a crafted page. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which validates only the submitted salt and applies the same check to multipart forms.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 28, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Separate submitted and response salts in UI filters

Fix merged in apache/roller PR #167 on 2026-09-05 — awaiting tagged release

https://github.com/apache/roller/pull/167

Vendor Advisories for CVE-2026-82380(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 35× in last 7d / 35× 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-10-04 03:28 UTCGHSA enrichment
  2. 2026-10-03 16:24 UTCEG score recompute
  3. 2026-10-03 16:24 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 05:21 UTCGHSA enrichment
  6. 2026-10-02 18:16 UTCGHSA enrichment
  7. 2026-10-02 18:16 UTCEG score recompute
  8. 2026-10-02 18:16 UTCGHSA enrichment
  9. 2026-10-02 18:16 UTCGHSA enrichment
  10. 2026-10-02 17:57 UTCEPSS rescore
  11. 2026-10-02 07:11 UTCGHSA enrichment
  12. 2026-10-01 20:08 UTCEG score recompute
  13. 2026-10-01 20:07 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 08:59 UTCGHSA enrichment
  16. 2026-09-30 21:55 UTCEG score recompute
  17. 2026-09-30 21:55 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 10:51 UTCGHSA enrichment
  20. 2026-09-29 23:46 UTCEG score recompute
  21. 2026-09-29 23:46 UTCGHSA enrichment
  22. 2026-09-29 12:38 UTCGHSA enrichment
  23. 2026-09-29 01:34 UTCEG score recompute
  24. 2026-09-29 01:34 UTCGHSA enrichment
  25. 2026-09-28 14:30 UTCGHSA enrichment
Show 10 more
  1. 2026-09-28 14:25 UTCEG score recompute
  2. 2026-09-28 14:25 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 13:43 UTCEG score recompute
  5. 2026-09-28 13:43 UTCGHSA enrichment
  6. 2026-09-28 09:32 UTCEG score recompute
  7. 2026-09-28 09:32 UTCGHSA enrichment
  8. 2026-09-28 08:29 UTCEG score recompute
  9. 2026-09-28 08:08 UTCEG score recompute
  10. 2026-09-28 08:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82380?
CVE-2026-82380 is a high vulnerability published on September 28, 2026. Cross-Site Request Forgery (CSRF) in Apache Roller 6.1.5 allows a remote attacker to cause a logged-in user to perform state-changing actions under the victim's authority, because the CSRF validation filters accept a request that does not submit the required salt token, validating instead against a…
When was CVE-2026-82380 disclosed?
CVE-2026-82380 was first published on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82380 actively exploited?
CVE-2026-82380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82380?
CVE-2026-82380 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82380?
An upstream fix for CVE-2026-82380 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-82380 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82380?

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