Audit-trail corruption via unvalidated login CSRF token
Published Sep 8, 2026 · Updated Sep 8, 2026
Login CSRF in Nozomi Networks Guardian and CMC before 26.3.0 allows remote authenticated users to corrupt audit attribution. The standard and SAML login handlers accept authentication requests without validating the anti-CSRF token, so a crafted link signs a victim into the attacker's account. A valid attacker account and victim interaction are required; subsequent victim actions are recorded under the attacker's identity, undermining the audit trail.
Summary
What happened
Login CSRF in Nozomi Networks Guardian and CMC before 26.3.0 allows remote authenticated users to corrupt audit attribution. The standard and SAML login handlers accept authentication requests without validating the anti-CSRF token, so a crafted link signs a victim into the attacker's account. A valid attacker account and victim interaction are required; subsequent victim actions are recorded under the attacker's identity, undermining the audit trail.
The record
- CVE
- CVE-2026-33920
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Vendor
- Nozomi Networks
- Product
- Guardian
- Classifications
- CWE-352, CAPEC-62, T1566.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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=0 <26.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo