CVE-2026-78425
HighCVSS 7.6Summary
Authorised users of outside applications behind the same corporate identity provider (IdP), such as a wiki, ticketing system, or expenses tool, can log into their system via SAML SSO. If that assertion is presented to NeuVector, NeuVector accepts it because the only thing distinguishing an assertion for NeuVector from an assertion for the wiki is the element, and the NotInAudience warning that reports the mismatch is never read.
Risk Assessment
An attacker with an account on any application behind the same IdP could gain access to NeuVector, leading to access control bypass and unauthorized access.
Recommendation
Update NeuVector to a version containing the SAML assertion validation fix and verify the IdP trust configuration.
Other vulnerabilities in NeuVector
See all- CVE-2026-78427Medium
The NeuVector admission webhook silently excludes containers from policy evaluation when their image path matches one of three hardcoded service mesh sidecar images. Since the image path is entirely controlled by the workload author, any user capable of deploying workloads can evade admission deny rules simply by naming their image path after one of these sidecar images.
- CVE-2026-78426Low
The NeuVector JWT verifier accepts noncanonical Base64URL encodings of the same RSA signature field. An attacker holding a valid JWT that has not expired, but was logged out of NeuVector, can continue using the non-expired token with equivalent spelling of the RSA signature field until the token validity expires.
- CVE-2026-25703High
NeuVector through 5.4.9 can potentially leak information from the manager /network/graph API due to missing authentication and cached data containing sensitive information.
Original NVD description (English source)
Authorised users of outside applications behind the same corporate identity provider (IdP), for example, a wiki, a ticketing system, an expenses tool, or anything they legitimately hold an account on can log into their system via SAML SSO. The IdP issues an assertion to them. If that assertion is presented to NeuVector, NeuVector accepts it because the only thing distinguishing "an assertion for NeuVector" from "an assertion for the wiki" is the element, and the `NotInAudience` warning that reports the mismatch is never read.