CVE-2025-6920: Red Hat AI Inference Server · Missing Authentication
Affects Red Hat AI Inference ServerSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2025-6920, organizations should first verify if their deployment of Red Hat AI Inference Server includes the vulnerable POST /invocations endpoint. Immediate steps include implementing network-level access controls such as IP whitelisting or VPN restrictions to limit exposure of the AI inference API to trusted users only. If patches become available from Red Hat, applying them promptly is critical. In the absence of official patches, organizations can implement API gateway solutions or reverse proxies that enforce API key validation on all endpoints, including /invocations, to ensure consistent authentication. Regularly auditing API endpoint configurations and access logs can help detect unauthorized access attempts. Additionally, segregating AI inference servers within secure network segments and employing strong monitoring and alerting for anomalous API usage patterns will reduce risk. Developers should review and update security policies to mandate authentication enforcement on all critical API functions. Finally, educating operational teams about this vulnerability and its implications will improve incident response readiness.
Description
A flaw was found in the authentication enforcement mechanism of a model inference API in ai-inference-server. All /v1/* endpoints are expected to enforce API key validation. However, the POST /invocations endpoint failed to do so, resulting in an authentication bypass. This vulnerability allows unauthorized users to access the same inference features available on protected endpoints, potentially exposing sensitive functionality or allowing unintended access to backend resources.