CVE-2026-118410VulnerabilityPublished 11 Nov 2026

Apache Roller · Resource Exposure

Source GCVE Database

Compare

Authoritative record:CVE-2026-118410· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 11 Nov 2026, 16:52 UTC

CVSS 3.1 base score

3.7Low

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (apache)	CVSS 3.1	3.7

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 11 Nov 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 11 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.

ghsa-g82c-vmxh-2c3f

What to do

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Roller	Affected >=4.0 <=6.1.6	Fixed in–
Mavenorg.apache.roller/roller`pkg:maven/org.apache.roller/roller`Other threats	Affected >=4.0 <=6.1.6	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.7 or later, where the issue is fixed by restricting search results to published entries only. Since AtomPub API is disabled by default, enabling it increases exposure risk and should be done cautiously. No other mitigations are specified.

Description

Apache Roller versions 4.0 through 6.1.6 have a vulnerability where an unauthenticated visitor can read blog entries that authors have withdrawn to draft status via the AtomPub API. Although the entry is removed from the weblog, it remains in the search index and is visible through public search. AtomPub is disabled by default. Upgrading to version 6.1.7 or later resolves this issue by ensuring only published entries appear in search results.

Impact

An unauthenticated attacker can read blog entries that authors have withdrawn to draft status, exposing potentially sensitive or unpublished content. The impact is limited to confidentiality (partial information disclosure) with no integrity or availability impact. The vulnerability requires network access and has a high attack complexity due to AtomPub being disabled by default.

Summary

This vulnerability in Apache Roller 4.0 through 6.1.6 involves exposure of resources to the wrong sphere, specifically allowing unauthenticated users to access withdrawn blog entries through the AtomPub API. The withdrawn entries remain indexed in the public search, thereby exposing content that should no longer be publicly accessible. The issue is addressed in Apache Roller 6.1.7 and later, which restricts search results to published entries only. AtomPub API is disabled by default, reducing exposure risk.

CWE-668Exposure of Resource to Wrong Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Authorization (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 11 Nov 2026, 16:52 UTC

WeaknessesCWE-668

Technical details

References

Community reviews

Related threats