VulnerabilityPublished 28 Sep 2026Updated 29 Sep 2026

CVE-2026-82386: Apache Roller · XML External Entity (XXE)

Affects Apache RollerSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.7 High · fixed in 6.1.6 : patch Apache Roller soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.1.6

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Roller	Affected =6.1.5	Fixed in–
Mavenorg.apache.roller/roller`pkg:maven/org.apache.roller/roller`Other threats	Affected =6.1.5	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache Roller version 6.1.6 or later, which includes a hardened XML parser that disables external entity resolution and document type declarations, effectively mitigating this vulnerability. No other configuration changes are required to address this issue.

Description

CVE-2026-82386 is a high-severity vulnerability in Apache Roller 6.1.5 involving improper restriction of XML External Entity (XXE) references. It allows a weblog administrator to read files accessible to the Roller process and access internal network addresses by importing a crafted OPML document. This occurs because the bookmark import parser does not disable external entity resolution. No special configuration is needed to exploit this; the vulnerability is triggered via the administrator bookmark-import action. Upgrading to Apache Roller 6.1.6 or later mitigates this issue by using a hardened parser that disables external entities and document type declarations.

Impact

An attacker with weblog administrator privileges can exploit this vulnerability to read sensitive files accessible by the Roller process and potentially access internal network resources. This can lead to information disclosure with high confidentiality impact. There is no impact on integrity or availability as per the CVSS vector. The vulnerability requires low attack complexity and privileges but no user interaction.

Summary

Apache Roller 6.1.5 suffers from an XML External Entity (XXE) vulnerability (CWE-611) due to the bookmark import parser not disabling external entity resolution. This flaw allows a weblog administrator to import a malicious OPML document that can read files accessible by the Roller process and reach internal network addresses. The vulnerability requires no non-default configuration and is exploitable through the administrator bookmark-import functionality. The issue is resolved in Apache Roller 6.1.6 and later versions by employing a parser that disables external entities and document type declarations.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Oct 2026, 21:00 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats