Skip to main content
VulnerabilityPublished Updated

CVE-2025-54982: Zscaler Authentication Server · Improper Verification of Cryptographic Signature

Affects Zscaler Authentication ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Zscaler Authentication ServerAffected
  • =0
Fixed in–

AI-suggested

Given the absence of an official patch at the time of disclosure, organizations should implement immediate compensating controls. These include: 1) Restrict network access to the Zscaler Authentication Server to trusted IP ranges and enforce strict firewall rules to limit exposure. 2) Enable multi-factor authentication (MFA) wherever possible to add an additional layer of verification beyond SAML tokens. 3) Monitor authentication logs for unusual or anomalous login patterns that may indicate exploitation attempts. 4) Employ anomaly detection and behavioral analytics to identify suspicious token usage or privilege escalations. 5) Coordinate with Zscaler support for any available interim fixes or configuration changes that can strengthen signature verification. 6) Prepare for rapid deployment of patches once released by testing updates in controlled environments. 7) Educate security teams about the vulnerability specifics to enhance incident response readiness. 8) Consider deploying additional identity federation validation tools or gateways that perform independent signature verification as a temporary safeguard. These targeted measures go beyond generic advice by focusing on network segmentation, enhanced monitoring, and layered authentication to reduce the attack surface and detect exploitation attempts early.

Description

An improper verification of cryptographic signature in Zscaler's SAML authentication mechanism on the server-side allowed an authentication abuse.

References

Community reviews

Loading reviews…