CVE-2026-53998

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-17. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-126621 (ENISA EUVD) · GHSA-gfv3-m769-5xm3 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Phoenix is an AI observability and evaluation platform. From 13.0.0 until 15.7.0, the applyChatTemplate GraphQL query passed attacker-controlled F-string templates to FStringTemplateFormatter._format, while DotDict.__getattr__ did not prevent traversal through Python private attributes. A crafted field could traverse object internals such as __class__, __init__, and __globals__ to read process environment variables and internal module state. The endpoint is unauthenticated on default installations, and any account can reach it when authentication is enabled. Exposure of PHOENIX_SECRET can allow administrative session-token forgery and decryption of credentials protected by keys derived from that secret. This issue is fixed in version 15.7.0.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 17, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Format String Injection in applyChatTemplate · Advisory · Arize-ai/phoenix · GitHub

https://github.com/Arize-ai/phoenix/security/advisories/GHSA-gfv3-m769-5xm3
GitHub release Patch Available

arize-phoenix: v15.7.0

Patch available: Arize-ai/phoenix arize-phoenix-v15.7.0

https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v15.7.0
GitHub pull request Patch Available

fix: prevent format-string injection in f-string template formatter

Patch available: Arize-ai/phoenix arize-phoenix-evals-v3.9.5 (PR #13197 merged 2026-05-13)

https://github.com/Arize-ai/phoenix/pull/13197
GitHub commit Patch Available

commit e7224a685589 (Arize-ai/phoenix)

Patch available: Arize-ai/phoenix arize-phoenix-evals-v3.9.5 (contains commit e7224a685589)

https://github.com/Arize-ai/phoenix/commit/e7224a685589f2ffae1fefcc68ff210bd6ad28b8

Vendor Advisories for CVE-2026-53998(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piparize-phoenix @ 15.7.0 (fixes >= 13.0.0, < 15.7.0)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
arize-phoenix13.0.2 ... 15.4.0 (59 versions)
  • 13.0.0 up to 15.7.0: fixed in 15.7.0
—

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 time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 21:21 UTCEchelonGraph re-scored
  2. 2026-11-21 21:21 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-11-20 22:22 UTCEchelonGraph re-scored
  5. 2026-11-20 22:22 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-11-19 23:18 UTCEchelonGraph re-scored
  8. 2026-11-19 23:18 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-11-19 21:25 UTCEchelonGraph re-scored
  10. 2026-11-19 21:24 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  11. 2026-11-19 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-11-18 22:27 UTCEchelonGraph re-scored
  13. 2026-11-18 22:27 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  14. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-11-17 23:28 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  16. 2026-11-17 20:46 UTCEchelonGraph re-scored
  17. 2026-11-17 20:46 UTCGHSA enrichmentGHSA-gfv3-m769-5xm3 · GitHub severity CRITICAL · GitHub CVSS 10.0
  18. 2026-11-17 19:26 UTCEchelonGraph re-scored
  19. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-11-16 21:02 UTCENISA EUVD ID recordedEUVD-2026-126621 · Source: ENISA EUVD
  21. 2026-11-16 20:28 UTCEchelonGraph re-scored
  22. 2026-11-16 19:59 UTCEchelonGraph re-scoredFirst assessed: 10.0 CRITICAL
  23. 2026-11-16 19:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53998?
CVE-2026-53998 is a critical-severity vulnerability; its CVE record was published on November 16, 2026. Phoenix is an AI observability and evaluation platform. From 13.0.0 until 15.7.0, the applyChatTemplate GraphQL query passed attacker-controlled F-string templates to FStringTemplateFormatter._format, while DotDict.__getattr__ did not prevent traversal through Python private attributes. A crafted…
When was the CVE record for CVE-2026-53998 published?
The CVE record for CVE-2026-53998 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-53998 actively exploited?
CVE-2026-53998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53998?
CVE-2026-53998 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53998?
A fix for CVE-2026-53998 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53998 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53998

Explore →

Is Your Infrastructure Affected by CVE-2026-53998?

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