The applyChatTemplate GraphQL query accepts an attacker-controlled F-string template, and the formatter can expose server-side data. The GitHub advisory lists versions from 13.0.0 as affected and 15.7.0 as patched.The advisory says default Phoenix installations expose this query without authentication. When authentication is enabled, any account can reach it. A successful attack could disclose PHOENIX_SECRET, which the report says signs session tokens and helps protect stored credentials.
What it allows
How Does CVE-2026-53998 Expose Phoenix Secrets?
NVD describes two linked failures: applyChatTemplate passes an untrusted F-string template to FStringTemplateFormatter._format, and DotDict.__getattr__ does not block access through Python private attributes. That combination can let a requester reach process environment variables and internal module state through the rendered response. The GitHub report says PHOENIX_SECRET could then support administrative session-token forgery and decryption of credentials protected by keys derived from that secret.
This is a confidentiality and follow-on account risk, rather than evidence of a confirmed compromise. The vendor record scores it CVSS 3.1 10.0 Critical. A vulnerability intelligence platform can help prioritize the affected deployments, while the Phoenix advisory remains the source for the fix.
What Is Known About Exploitation?
The advisory includes a proof-of-concept description, but it does not establish attacks against a deployed organization. Brandefense Blackhole counted two dark-chat posts mentioning CVE-2026-53998 from 19 August through 17 November 2026. The unit is posts; discussion alone does not demonstrate exploitation.
The CISA KEV catalog snapshot dated 13 November 2026 did not list this CVE. That snapshot predates NVD publication on 16 November, so it should not be used as a current exploitation verdict. Treat the exploitation status as unknown and prioritize by exposure, potential secret impact, and the available fix.
Who is affected
Which Phoenix Versions Are Affected by CVE-2026-53998?
The GitHub advisory lists arize-phoenix 13.0.0 and later as affected, with 15.7.0 as the patched release. This makes 13.0.0 up to, but excluding, 15.7.0 the advisory-based update range. The report body names 14.8.0 as its latest confirmed vulnerable test, which is a narrower observation than the advisory table.
Check the version actually running in each Phoenix deployment, including containers and managed builds. The advisory gives one cross-major range, without separate stable fix thresholds for 13.x and 14.x. Compare the installed package with its current advisory and verify the running build after updating.
How Should Defenders Respond?
Prioritize reachable default installations, because the advisory says the affected query is available without credentials in that configuration. Authenticated deployments still need the update because any account can reach the query. Restrict access to Phoenix while scheduling the update if exposure cannot be removed immediately.
Update arize-phoenix to 15.7.0 or a later patched release, then confirm the running package version. As a Brandefense recommendation, review API and application logs for suspicious template use and assess whether PHOENIX_SECRET or stored credentials may have been disclosed. If investigation supports exposure, follow supported procedures to rotate affected secrets and revoke sessions; see the credential compromise and patch management references.
Timeline
- 2026-11-09
The GitHub security advisory was published with affected and patched version information.
- 2026-11-16
NVD published the CVE record, describing the formatter and private-attribute traversal.
What to do
-
Inventory Phoenix deployments
Record each running arize-phoenix version, its network exposure, and whether authentication is enabled. Include container images and managed deployments.
-
Patch the reachable instances first
Update affected installations to version 15.7.0 or a later patched release. Restrict network access if the update cannot be completed immediately.
-
Verify the running version
After deployment, check the version running in each instance and confirm it is 15.7.0 or later. Recheck any rebuilt image before restoring access.
-
Investigate possible secret exposure
Review available API and application logs. If exposure is supported by evidence, rotate affected secrets and revoke sessions using the vendor-supported procedure.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-53998 in Brandefense Atlas
The Atlas record of CVE-2026-53998: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Which Phoenix version fixes CVE-2026-53998?
The GitHub advisory lists arize-phoenix 15.7.0 as patched. Verify that every deployed instance runs 15.7.0 or a later patched release.
Does Phoenix authentication prevent this vulnerability?
No. The report says default deployments require no credentials, while any account can access the affected query when authentication is enabled.
Does the advisory confirm active exploitation?
The advisory documents a proof of concept and impact, but does not establish attacks against deployed organizations. Exploitation status remains unknown.
Why does PHOENIX_SECRET matter?
The advisory says this secret signs JWT sessions and derives a key protecting stored credentials. Exposure could enable admin session forgery and credential decryption.
Sources
- Format String Injection in applyChatTemplateGitHub Security Advisory
- CVE-2026-53998 RecordNVD
- Known Exploited Vulnerabilities CatalogCISA