Cross-user session takeover via shared SSO token key
Published Sep 17, 2026 · Updated Sep 28, 2026
Session mix-up in SUSE NeuVector SAML/OIDC login allows remote attackers to receive another user's session during concurrent SSO logins. The Manager caches controller-issued JWTs under one shared "samlSso" key, letting overlapping authentication callbacks overwrite the token before browser retrieval. The race requires SAML or OIDC authentication, a concurrent second login, and completed identity-provider interaction; the recipient gains the other user's assigned roles and permissions.
Summary
What happened
Session mix-up in SUSE NeuVector SAML/OIDC login allows remote attackers to receive another user's session during concurrent SSO logins. The Manager caches controller-issued JWTs under one shared "samlSso" key, letting overlapping authentication callbacks overwrite the token before browser retrieval. The race requires SAML or OIDC authentication, a concurrent second login, and completed identity-provider interaction; the recipient gains the other user's assigned roles and permissions.
The record
- CVE
- CVE-2026-78428
- Published
- Sep 17, 2026
- Updated
- Sep 28, 2026
- Vendor
- SUSE
- Product
- NeuVector
- Classifications
- CWE-384, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<5.6.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started