PatchSiren cyber security CVE debrief
CVE-2026-44990 apostrophecms CVE debrief
ApostropheCMS's sanitize-html library versions prior to 2.17.4 have a vulnerability that can turn attacker-controlled content inside a disallowed `xmp` element into live HTML or JavaScript, leading to stored XSS. This issue is patched in version 2.17.4. The vulnerability allows an attacker to inject malicious code, which can then be executed by the application, potentially leading to unauthorized access or data breaches. Defenders should assess their exposure and prioritize upgrading to version 2.17.4 or later to prevent attacks.
- Vendor
- apostrophecms
- Product
- sanitize-html
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-12
- Original CVE updated
- 2026-09-10
- Advisory published
- 2026-06-12
- Advisory updated
- 2026-09-10
Who should care
Defenders responsible for ApostropheCMS installations and applications using sanitize-html should assess exposure and prioritize upgrading to version 2.17.4 or later. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations through normal and
Why it matters
CVE-2026-44990 is a critical vulnerability in ApostropheCMS's sanitize-html library that can lead to stored XSS attacks. Defenders should prioritize upgrading to version 2.17.4 or later to prevent attacks.
- Stored XSS attacks can lead to user data compromise
- Defenders must verify affected versions and upgrade to 2.17.4 or later
- Applications rendering sanitized output back to users are at risk
Technical summary
The sanitize-html library in ApostropheCMS has a vulnerability that allows attacker-controlled content to be turned into live HTML or JavaScript, leading to stored XSS. This issue is patched in version 2.17.4. The vulnerability is caused by the library's inability to properly sanitize user input, allowing for the injection of malicious code. The patched version fixes this issue by properly sanitizing user input, preventing the injection of malicious code. Defenders should prioritize upgrading to version 2.17.4 or later to prevent stored XSS attacks.
Defensive priority
Defenders should prioritize upgrading to sanitize-html version 2.17.4 or later to prevent stored XSS attacks.
Recommended defensive actions
- Upgrade to sanitize-html version 2.17.4 or later
- Review and update affected applications that render sanitized output back to users
- Monitor for potential stored XSS attacks
- Verify affected versions and upgrade to 2.17.4 or later
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its impact, and the patched version. The vulnerability is a result of the library's inability to properly sanitize user input, allowing for the injection of malicious code. The CVE record and NVD entry also provide information on the affected versions and the patched version.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-44990 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-44990
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-44990 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44990
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-rpr9-rxv7-x643
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:36882
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:36883
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:40262
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:41031
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:41055
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:41064
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:41066
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.