CVE-2026-92213

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability was detected in a2ui-project a2ui up to 0.10.6. This impacts the function z.any of the file renderers/web_core/src/v0_9/schema/server-to-client.ts of the component Angular Renderer. Performing a manipulation of the argument primaryColor results in injection. The attack is possible to be carried out remotely. The patch is named fb8e85aec78d04e81feb9992a57638ca1ec4dc1b. It is suggested to install a patch to address this issue.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
25(Track)
EG Risk 25/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 computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

GitHub - a2ui-project/a2ui · GitHub

https://github.com/a2ui-project/a2ui/
github_commit

commit fb8e85aec78d (a2ui-project/a2ui)

Fix landed in a2ui-project/a2ui commit fb8e85aec78d — awaiting tagged release

https://github.com/a2ui-project/a2ui/commit/fb8e85aec78d04e81feb9992a57638ca1ec4dc1b
github_pr

fix(web_core): validate surface theme against catalog themeSchema

Fix merged in a2ui-project/a2ui PR #2367 on 2026-09-14 — awaiting tagged release

https://github.com/a2ui-project/a2ui/pull/2367
generic

[BUG]: `createSurface.theme` values stored without validation and consumed as CSS values · Issue #2293 · a2ui-project/a2ui · GitHub

https://github.com/a2ui-project/a2ui/issues/2293

Vendor Advisories for CVE-2026-92213(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 15× in last 7d / 15× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:23 UTCGHSA enrichment
  3. 2026-09-17 19:43 UTCEG score recompute
  4. 2026-09-17 19:43 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-16 21:02 UTCEG score recompute
  7. 2026-09-16 21:02 UTCGHSA enrichment
  8. 2026-09-16 19:49 UTCEG score recompute
  9. 2026-09-16 19:49 UTCGHSA enrichment
  10. 2026-09-16 18:05 UTCEG score recompute
  11. 2026-09-16 18:05 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 01:22 UTCEG score recompute
  14. 2026-09-16 00:58 UTCEG score recompute
  15. 2026-09-16 00:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92213?
CVE-2026-92213 is a medium vulnerability published on September 16, 2026. A vulnerability was detected in a2ui-project a2ui up to 0.10.6. This impacts the function z.any of the file renderers/webcore/src/v09/schema/server-to-client.ts of the component Angular Renderer. Performing a manipulation of the argument primaryColor results in injection. The attack is possible to…
When was CVE-2026-92213 disclosed?
CVE-2026-92213 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92213 actively exploited?
CVE-2026-92213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2026-92213?
CVE-2026-92213 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-92213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92213

Explore →

Is Your Infrastructure Affected by CVE-2026-92213?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs