
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 13.0.0, < 15.7.0
Patched in 15.7.0
Details
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.
os.environ including the admin credentials hardcoded in phoenix.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.
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
applyChatTemplate GraphQL 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 } } }
}
}
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
EPSS, exploit probability
Low0.36%
estimated chance of real-world exploitation in the next 30 days, higher than 29.9% of every CVE FIRST.org scores
Refreshed 11/17/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More pip advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.