Answer in brief
CVE-2025-40900 records a Unknown severity vulnerability in Angular template injection in Reports in Guardian/CMC before 26.1.0. The current sources do not mark it as known exploited. The current feed maps Nozomi Networks/CMC (generic), Nozomi Networks/Guardian (generic), Siemens/RUGGEDCOM APE1808 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Nozomi Networks/CMC (generic), Nozomi Networks/Guardian (generic), Siemens/RUGGEDCOM APE1808 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Nozomi Networks/CMCgeneric | >=0 <26.1.0 | 26.1.0 |
| Nozomi Networks/Guardiangeneric | >=0 <26.1.0 | 26.1.0 |
| Siemens/RUGGEDCOM APE1808generic | >=0 <* | * |
Published upstream
May 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
An Angular template injection vulnerability was discovered in the Reports functionality due to improper validation of an input parameter. An authenticated user with report privileges can define a malicious report containing an Angular template payload, or a victim can be socially engineered to import a malicious report template. When the victim views or imports the report, the Angular template executes in their browser context, allowing the attacker to modify application data, or disrupt application availability. Full XSS exploitation and direct information disclosure are prevented by the existing input validation and Content Security Policy configuration.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-40900 records a Unknown severity vulnerability in Angular template injection in Reports in Guardian/CMC before 26.1.0. The current sources do not mark it as known exploited. The current feed maps Nozomi Networks/CMC (generic), Nozomi Networks/Guardian (generic), Siemens/RUGGEDCOM APE1808 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Nozomi Networks/CMC (generic), Nozomi Networks/Guardian (generic), Siemens/RUGGEDCOM APE1808 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Nozomi Networks/CMCgeneric | >=0 <26.1.0 | 26.1.0 |
| Nozomi Networks/Guardiangeneric | >=0 <26.1.0 | 26.1.0 |
| Siemens/RUGGEDCOM APE1808generic | >=0 <* | * |
Published upstream
May 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
An Angular template injection vulnerability was discovered in the Reports functionality due to improper validation of an input parameter. An authenticated user with report privileges can define a malicious report containing an Angular template payload, or a victim can be socially engineered to import a malicious report template. When the victim views or imports the report, the Angular template executes in their browser context, allowing the attacker to modify application data, or disrupt application availability. Full XSS exploitation and direct information disclosure are prevented by the existing input validation and Content Security Policy configuration.
Quoted source text, attributed separately from HOL analysis.