Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.45% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-22610High confidence
Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
angular · angular
Official source articles: Siemens SSA-253495 ↗ · Siemens SSA-485750 ↗ · GitHub GHSA-JRMJ-C5CX-3CW6 ↗. Check the applicable product and release in the original source.
8.5HighCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs angular angular and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
Distribution package intelligence
4 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | angular.js | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | angular.js | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | angular.js | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | angular.js | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges20 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npm@angular/compiler | >= 21.1.0-next.0, < 21.1.0-rc.0 | 21.1.0-rc.0 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/compiler | >= 21.0.0-next.0, < 21.0.7 | 21.0.7 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/compiler | >= 20.0.0-next.0, < 20.3.16 | 20.3.16 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/compiler | >= 19.0.0-next.0, < 19.2.18 | 19.2.18 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/compiler | <= 18.2.14 | Not stated | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/compiler | SEMVER: introduced 21.1.0-next.0; fixed 21.1.0-rc.0 | 21.1.0-rc.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/compiler | SEMVER: introduced 21.0.0-next.0; fixed 21.0.7 | 21.0.7 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/compiler | SEMVER: introduced 20.0.0-next.0; fixed 20.3.16 | 20.3.16 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/compiler | SEMVER: introduced 19.0.0-next.0; fixed 19.2.18 | 19.2.18 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/compiler | SEMVER: introduced 0; last affected 18.2.14 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/core | >= 21.1.0-next.0, < 21.1.0-rc.0 | 21.1.0-rc.0 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/core | >= 21.0.0-next.0, < 21.0.7 | 21.0.7 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/core | >= 20.0.0-next.0, < 20.3.16 | 20.3.16 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/core | >= 19.0.0-next.0, < 19.2.18 | 19.2.18 | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/core | <= 18.2.14 | Not stated | GitHub advisory ↗upstream repository advisory · 9 Jun 2026 |
| npm@angular/core | SEMVER: introduced 21.1.0-next.0; fixed 21.1.0-rc.0 | 21.1.0-rc.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/core | SEMVER: introduced 21.0.0-next.0; fixed 21.0.7 | 21.0.7 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/core | SEMVER: introduced 20.0.0-next.0; fixed 20.3.16 | 20.3.16 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/core | SEMVER: introduced 19.0.0-next.0; fixed 19.2.18 | 19.2.18 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npm@angular/core | SEMVER: introduced 0; last affected 18.2.14 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
SSA-253495 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0
The vendor explicitly identifies these products as affected by this CVE.
- RUGGEDCOM RST2428P (6GK6242-6PA00)
- Summary
- Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
- Remediation
- Update to V4.0 or later version
SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
The vendor explicitly identifies these products as affected by this CVE.
- SIDIS Prime
- Summary
- Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
- Remediation
- Update to V4.0.800 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
What
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
Why
Attacker-controlled content can reach a browser as executable script without sufficient output encoding or sanitisation.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
Why
Attacker-controlled content can reach a browser as executable script without sufficient output encoding or sanitisation.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Active interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-79 ↗
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04
Evidence and provenance
Published 10 Jan 2026 · Last source change 2 Jun 2026, 13:00 UTC · CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-1698
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Siemens ProductCERT ↗
- Before
- >= 21.1.0-next.0, < 21.1.0-rc.0; >= 21.0.0-next.0, < 21.0.7; >= 20.0.0-next.0, < 20.3.16; < 19.2.18 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- >= 21.1.0-next.0, < 21.1.0-rc.0; >= 21.0.0-next.0, < 21.0.7; >= 20.0.0-next.0, < 20.3.16; < 19.2.18 · Fixed: Update to V4.0.800 or later version
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.