Answer in brief
CVE-2026-55566 records a Medium severity (CVSS 4.3) vulnerability in Yamcs has DOM XSS in Extension Routing. The current sources do not mark it as known exploited. The current feed maps org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. 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 org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.yamcs:yamcs-coremaven | >=5.13.0,<=5.13.1 | 5.13.2 |
| org.yamcs:yamcs-coremaven | <=5.12.7 | 5.12.8 |
Published upstream
Aug 28, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
**Attack type**: Unauthenticated remote **Impact**: Execution of arbitrary JavaScript in a user’s browser. **Affected components**: extension.matcher.ts:12, extension.component.ts:40, app.component.ts:134. Yamcs is vulnerable to cross-site scripting in the /ext URL endpoint. By inputting specially crafted code into the URL, an attacker can execute arbitrary JavaScript code in a user’s browser. This URL may be sent to a user via a phishing email. <img width="940" height="294" alt="image" src="https://github.com/user-attachments/assets/d886d65c-9bb5-4599-ac11-55db83aafc0e" /> Steps to Reproduce: 1. Start a Yamcs instance. 2. Insert the following URL into the browser and press enter (change ‘myproject’ to the name of your instance): ``` http://localhost:8090/ext/img%20src%3Dx%20onerror%3Dalert%281%29?c=myproject ``` 3. You will receive an alert with the number ‘1’ in it. Recommendations: 1. Use document.createElement instead of innerHTML in extension.component.ts. 2. Validate the extension against registered plugin IDs. 3. Enforce a strict custom-element-name regex before mounting.
Quoted source text, attributed separately from HOL analysis.