Authentication bypass via improper CAS signature verification
Published May 13, 2026 · Updated May 13, 2026
Authentication bypass in Palo Alto Networks PAN-OS 10.2, 11.1, 11.2, and 12.1 allows remote attackers to bypass login controls. The CAS authentication path improperly verifies a cryptographic signature, but Palo Alto Networks has not disclosed the specific message, token, or code locus involved. Exposure requires a CAS authentication profile attached to a login interface; successful exploitation grants that interface's protected access, with management access posing the greatest risk.
Summary
What happened
Authentication bypass in Palo Alto Networks PAN-OS 10.2, 11.1, 11.2, and 12.1 allows remote attackers to bypass login controls. The CAS authentication path improperly verifies a cryptographic signature, but Palo Alto Networks has not disclosed the specific message, token, or code locus involved. Exposure requires a CAS authentication profile attached to a login interface; successful exploitation grants that interface's protected access, with management access posing the greatest risk.
The record
- CVE
- CVE-2026-0265
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Palo Alto Networks
- Product
- PAN-OS
- Classifications
- CWE-347, CAPEC-115, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 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=10.2.0 <10.2.18-h6, 10.2.16-h7, 10.2.13-h21, 10.2.10-h36, 10.2.7-h34 changes=[{"at":"10.2.7-h34","status":"unaffected"},{"at":"10.2.10-h36","status":"unaffected"},{"at":"10.2.13-h21","status":"unaffected"},{"at":"10.2.16-h7","status":"unaffected"},{"at":"10.2.18-h6","status":"unaffected"}]
- Affected versionversion=11.1.0 <11.1.15, 11.1.13-h5, 11.1.10-h25, 11.1.7-h6, 11.1.6-h32, 11.1.4-h33 changes=[{"at":"11.1.4-h33","status":"unaffected"},{"at":"11.1.6-h32","status":"unaffected"},{"at":"11.1.7-h6","status":"unaffected"},{"at":"11.1.10-h25","status":"unaffected"},{"at":"11.1.13-h5","status":"unaffected"},{"at":"11.1.15","status":"unaffected"}]
- Affected versionversion=11.2.0 <11.2.12, 11.2.10-h6, 11.2.7-h13, 11.2.4-h17 changes=[{"at":"11.2.4-h17","status":"unaffected"},{"at":"11.2.7-h13","status":"unaffected"},{"at":"11.2.10-h6","status":"unaffected"},{"at":"11.2.12","status":"unaffected"}]
- Affected versionversion=12.1.0 <12.1.7, 12.1.4-h5 changes=[{"at":"12.1.4-h5","status":"unaffected"},{"at":"12.1.7","status":"unaffected"}]
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