A vulnerability was determined in a2ui-project a2ui up to 0.10.6. This affects the function processMessages of the file renderers/web_core/src/v0_9/processing/message-processor.ts of the component Message Parsing. This manipulation causes dynamically-determined object attributes. The attack can be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-92217
Score 6.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026[BUG]: v0.9 message processor skips envelope schema validation and commits unknown component types · Issue #2297 · a2ui-project/a2ui · GitHub
https://github.com/a2ui-project/a2ui/issues/2297Vendor Advisories for CVE-2026-92217(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:34 UTCEG score recompute
- 2026-09-18 19:34 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 18:26 UTCEG score recompute
- 2026-09-17 18:26 UTCGHSA enrichment
- 2026-09-17 18:00 UTCEG score recompute
- 2026-09-17 18:00 UTCGHSA enrichment
- 2026-09-16 18:05 UTCEG score recompute
- 2026-09-16 18:05 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 02:25 UTCEG score recompute
- 2026-09-16 02:03 UTCEG score recompute
- 2026-09-16 02:02 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92217?
When was CVE-2026-92217 disclosed?
Is CVE-2026-92217 actively exploited?
What is the CVSS score of CVE-2026-92217?
How do I remediate CVE-2026-92217?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92217
Is Your Infrastructure Affected by CVE-2026-92217?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.