Server-Side Request Forgery (SSRF) in Apache Roller 6.1.5 allows an authenticated user with entry-editing rights on a weblog to cause outbound HTTP requests to attacker-chosen destinations through legacy outbound Trackback and entry enclosure handling. The Trackback control is hidden in the standard UI, but its action remains directly reachable; the enclosure path is relevant only when an author supplies an enclosure URL. No non-default server configuration is required, and the default empty Trackback allow-list permits all destinations. Requests can reach loopback and private-network addresses, while enclosure handling exposes response status, content type, and length. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which removes the outbound trackback action and stops dereferencing enclosure URLs.
CVE-2026-82375
Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. A secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 7.4
- EG Score
- 7.4HIGHhigh confidence
- EG Risk
- 33EG Risk 33/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 computedSeverity74% × 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.4%
- EPSS %ILE
- 28th
- 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 (3)
Auto-updated Sep 28, 2026Remove legacy outbound trackback action
Fix merged in apache/roller PR #163 on 2026-09-05 — awaiting tagged release
https://github.com/apache/roller/pull/163Store enclosure metadata without fetching remote URLs
Fix merged in apache/roller PR #175 on 2026-09-05 — awaiting tagged release
https://github.com/apache/roller/pull/175Vendor Advisories for CVE-2026-82375(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 31× in last 7d / 36× 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.
- 2026-10-05 07:47 UTCEG score recompute
- 2026-10-05 07:47 UTCGHSA enrichment
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 19:24 UTCGHSA enrichment
- 2026-10-04 07:00 UTCGHSA enrichment
- 2026-10-03 18:37 UTCEG score recompute
- 2026-10-03 18:37 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 06:14 UTCEG score recompute
- 2026-10-03 06:14 UTCGHSA enrichment
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-02 17:51 UTCGHSA enrichment
- 2026-10-02 05:29 UTCEG score recompute
- 2026-10-02 05:29 UTCGHSA enrichment
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 17:04 UTCGHSA enrichment
- 2026-10-01 04:41 UTCGHSA enrichment
- 2026-09-30 16:17 UTCEG score recompute
- 2026-09-30 16:17 UTCGHSA enrichment
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-30 03:40 UTCEG score recompute
- 2026-09-30 03:40 UTCGHSA enrichment
- 2026-09-29 15:15 UTCGHSA enrichment
- 2026-09-29 02:53 UTCEG score recompute
- 2026-09-29 02:53 UTCGHSA enrichment
Show 11 moreShow fewer
- 2026-09-28 14:30 UTCGHSA enrichment
- 2026-09-28 14:25 UTCEG score recompute
- 2026-09-28 14:25 UTCGHSA enrichment
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 13:44 UTCEG score recompute
- 2026-09-28 13:44 UTCGHSA enrichment
- 2026-09-28 09:32 UTCEG score recompute
- 2026-09-28 09:32 UTCGHSA enrichment
- 2026-09-28 08:29 UTCEG score recompute
- 2026-09-28 08:08 UTCEG score recompute
- 2026-09-28 08:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-82375?
When was CVE-2026-82375 disclosed?
Is CVE-2026-82375 actively exploited?
What is the CVSS score of CVE-2026-82375?
How do I remediate CVE-2026-82375?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82375
Is Your Infrastructure Affected by CVE-2026-82375?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.