Quick answers
- Is CVE-2026-78425 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78425 being exploited in the wild.
- How severe is CVE-2026-78425?
- Informational severity, with a CVSS score of 7.6, published 17 September 2026.
- Which products and versions are affected?
- NeuVector NeuVector <=5.6.1.
- Is there a fix for CVE-2026-78425?
- A patch was published on 2026-09-16: Patches released: v5.6.2, v5.5.4, v5.4.11 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78425 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-78425?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
NeuVector's SAML SSO implementation fails to properly validate the SAML Audience element, which is meant to restrict an assertion to a specific service provider (SP). When a user authenticates via a corporate identity provider (IdP), the IdP issues an assertion containing an Audience field tied to a different application (e.g., a wiki or ticketing system). NeuVector receives this assertion but does not enforce the Audience restriction—it only logs a `NotInAudience` warning that goes unread. An attacker with legitimate credentials for any other SAML-enabled application behind the same IdP can present that application's SAML assertion to NeuVector and gain unauthorized access. The vulnerability requires the attacker to have valid credentials for another SAML-backed application and network access to NeuVector. Patches are available in v5.6.2, v5.5.4, v5.4.11 and later, which introduce configurable Audience URI validation.
Affected products
- NeuVector NeuVector <=5.6.1
Timeline
- 2026-09-16: disclosed
- 2026-09-16: patched: Patches released: v5.6.2, v5.5.4, v5.4.11