CVE-2026-59728: CWE-91: XML Injection (aka Blind XPath Injection) in withastro astro
Astro is a web framework for content-driven websites. In versions 1.0.0 through 4.0.18, the source.title and enclosure.type item fields in packages/astro-rss/src/index.ts are interpolated directly into XML template strings without XML-character escaping before being parsed by fast-xml-parser. Both fields are validated only as z.string(), placing no restriction on XML special characters. An attacker who controls these values can inject arbitrary XML into the generated RSS feed: a value containing " can break out of an attribute (as with enclosure.type), and a value containing </source> can close an element early and inject additional nodes (as with source.title). This corrupts feed structure, injects false metadata (for example, a fake <link> pointing to a malicious URL), and can cause feed readers to misparse or display attacker-controlled content. In SSR mode (output: 'server'), the poisoned feed is served on every request to all subscribers. This issue has been fixed in version 4.0.19.
AI Analysis
Technical Summary
Astro, a web framework for content-driven websites, versions 1.0.0 through 4.0.18 improperly handle the source.title and enclosure.type fields in RSS feed XML templates by directly interpolating them without XML-character escaping. These fields are only validated as strings without restrictions on XML special characters. An attacker controlling these fields can inject arbitrary XML, breaking out of attributes or closing elements early, resulting in corrupted feed structure and injection of false metadata such as malicious links. This vulnerability is identified as CWE-91 (XML Injection) and has a CVSS 3.1 base score of 4.3 (medium severity). The vulnerability was fixed in version 4.0.19.
Potential Impact
An attacker who can control the source.title or enclosure.type fields can inject arbitrary XML into the RSS feed generated by Astro, corrupting the feed structure and injecting false metadata. This can cause feed readers to misparse or display attacker-controlled content, potentially misleading users or redirecting them to malicious URLs. In server-side rendering mode, the poisoned feed is served to all subscribers on every request, amplifying the impact. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Astro version 4.0.19. Users should upgrade to version 4.0.19 or later to remediate this issue. Until upgrading, avoid using untrusted input in the source.title and enclosure.type fields or implement proper XML character escaping before interpolation. Patch status is not explicitly stated in the vendor advisory, but the fix is confirmed in version 4.0.19.
CVE-2026-59728: CWE-91: XML Injection (aka Blind XPath Injection) in withastro astro
Description
Astro is a web framework for content-driven websites. In versions 1.0.0 through 4.0.18, the source.title and enclosure.type item fields in packages/astro-rss/src/index.ts are interpolated directly into XML template strings without XML-character escaping before being parsed by fast-xml-parser. Both fields are validated only as z.string(), placing no restriction on XML special characters. An attacker who controls these values can inject arbitrary XML into the generated RSS feed: a value containing " can break out of an attribute (as with enclosure.type), and a value containing </source> can close an element early and inject additional nodes (as with source.title). This corrupts feed structure, injects false metadata (for example, a fake <link> pointing to a malicious URL), and can cause feed readers to misparse or display attacker-controlled content. In SSR mode (output: 'server'), the poisoned feed is served on every request to all subscribers. This issue has been fixed in version 4.0.19.
CVSS v3.1
Score 4.3medium
Affected software
withastro
astro
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Astro, a web framework for content-driven websites, versions 1.0.0 through 4.0.18 improperly handle the source.title and enclosure.type fields in RSS feed XML templates by directly interpolating them without XML-character escaping. These fields are only validated as strings without restrictions on XML special characters. An attacker controlling these fields can inject arbitrary XML, breaking out of attributes or closing elements early, resulting in corrupted feed structure and injection of false metadata such as malicious links. This vulnerability is identified as CWE-91 (XML Injection) and has a CVSS 3.1 base score of 4.3 (medium severity). The vulnerability was fixed in version 4.0.19.
Potential Impact
An attacker who can control the source.title or enclosure.type fields can inject arbitrary XML into the RSS feed generated by Astro, corrupting the feed structure and injecting false metadata. This can cause feed readers to misparse or display attacker-controlled content, potentially misleading users or redirecting them to malicious URLs. In server-side rendering mode, the poisoned feed is served to all subscribers on every request, amplifying the impact. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Astro version 4.0.19. Users should upgrade to version 4.0.19 or later to remediate this issue. Until upgrading, avoid using untrusted input in the source.title and enclosure.type fields or implement proper XML character escaping before interpolation. Patch status is not explicitly stated in the vendor advisory, but the fix is confirmed in version 4.0.19.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-06T15:34:16.917Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a67c1be9c2644c7f8cb123f
Added to database: 07/27/2026, 20:38:22 UTC
Last enriched: 07/29/2026, 23:55:27 UTC
Last updated: 09/11/2026, 07:31:54 UTC
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.