CVE-2026-53998 is a critical-severity (CVSS 10) CWE-134 vulnerability in arize-phoenix. A fix is available for arize-phoenix — see the affected versions and patch details below.
Phoenix: Format String Injection in applyChatTemplate
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-53998.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
arize-phoenixReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
- Summary
A format string injection vulnerability in the applyChatTemplate GraphQL endpoint allows an attacker to read server-side environment variables, cryptographic secrets, and internal module attributes directly from the API response. On default Phoenix installations where authentication is disabled the endpoint is reachable with no credentials. On auth-enabled deployments, any account regardless of privilege level is sufficient to exploit it.
- Impact
Server filesystem paths, loaded Python module names, and internal configuration constants are fully disclosed, an attacker with network access can read the full server
os.environincluding the admin credentials hardcoded inphoenix.auth.
Successful exploitation allows an attacker to extract PHOENIX_SECRET, the master key used to sign all JWTs and derive the Fernet encryption key protecting stored credentials (LLM API keys, OAuth tokens). With this key, an attacker can forge admin-level session tokens and decrypt all secrets stored in the database.
- Affected Versions
First vulnerable release: arize-phoenix-v13.0.0 (2026-02-13) Latest confirmed vulnerable release: arize-phoenix-v14.8.0 (2026-04-17)
-
Affected Component
applyChatTemplateGraphQL query endpoint (src/phoenix/server/api/queries.py:1638)FStringTemplateFormatter._format()template rendering function (src/phoenix/utilities/template_formatters.py:272)DotDict.__getattr__()ineffective attribute access control (src/phoenix/utilities/template_formatters.py:90) -
Proof of Concept payload as txt with an image performing the exploit below.
<img width="1574" height="766" alt="PoC-Phoenix" src="https://github.com/user-attachments/assets/55f56325-4c26-4c96-8aa9-89e44ff1ba53" /> -
Payload:
{
"query": "query($t: PromptChatTemplateInput!, $o: PromptTemplateOptions!) { applyChatTemplate(template: $t, templateOptions: $o) { messages { content { ... on TextContentPart { text { text } } } } } }",
"variables": {
"t": { "messages": [{ "role": "USER", "content": [{ "text": { "text": "{u.__class__.__bases__[0].__init__.__globals__[_os].environ}" } }] }] },
"o": { "format": "F_STRING", "variables": { "u": { "x": 1 } } }
}
}
- Suggested Fix
Three mitigations are recommended in combination: restrict attribute traversal at the Formatter.get_field() level (not the wrapper class), add IsAuthenticated permission to the applyChatTemplate resolver, and limit F_STRING format to trusted system-defined templates only.
Best Regards, Omar
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | arize-phoenix | ≥ 13.0.0&&< 15.7.0 | 15.7.0pip install --upgrade 'arize-phoenix==15.7.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for arize-phoenix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update arize-phoenix to 15.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53998 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-53998 in your dependencies?
Find it across PyPI, including transitive dependencies.