Palo Alto Networks PAN-OS Authentication Bypass Vulnerability
Exploited since 2025-02-18. 2 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: blocked.
An authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web… More
An authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web interface and invoke certain PHP scripts. While invoking these PHP scripts does not enable remote code execution, it can negatively impact integrity and confidentiality of PAN-OS. You can greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practices deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 . This issue does not affect Cloud NGFW or Prisma Access software.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 4.0Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality and low impact on integrity.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityNo built-in defences have to be bypassed; the attack works reliably.Low
- Attack requirementsThe attack works without any special deployment or timing conditions.None
- Privileges requiredNo account or login is needed.None
- User interactionNo one has to click or open anything; the attack works on its own.None
- Confidentiality impact (vulnerable system)An attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impact (vulnerable system)An attacker can change some data, but with limited control or limited effect.Low
- Availability impact (vulnerable system)The component keeps working normally.None
- Confidentiality impact (other systems)Other systems' data is not exposed.None
- Integrity impact (other systems)Other systems' data cannot be changed.None
- Availability impact (other systems)Other systems keep working normally.None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:C/RE:M/U:RedAlso in the vector: Automatable: No · Recovery: User · Value density: Concentrated · Vulnerability response effort: Moderate · Provider urgency: Red
Attackers are exploiting this in the wild.
Attackers can script the attack end to end and hit many targets at once.
A successful attack gives limited control over the affected software or limited access to its data.
Public exploits
1 found- NucleiCVE-2025-0108.yamldetection template, replayed in our lab
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-02-12CVE publishedCVE List
- 2025-02-18Added to CISA KEVConfirmed exploitation in the wild
- 2025-02-24Cloudflare ships a rulePalo Alto Networks - Auth Bypass - CVE:CVE-2025-0108
- 2025-03-11F5 ships a rulePalo Alto PAN-OS Management Web Authentication Bypass (3)
- 2026-11-02Our test: OWASP Core Rule Set blocked itparanoia level 1, anomaly threshold 5, default CRS settings
- 2026-11-02Our test: OWASP Core Rule Set blocked itparanoia level 2, anomaly threshold 5, default CRS settings
Vendor statements
QuotedCloudflareWAF Managed Rules
First rule 2025-02-24, 12 days after the CVE was published.
Palo Alto Networks - Auth Bypass - CVE:CVE-2025-0108. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-03-11, 27 days after the CVE was published.
Added: signature 200013108 "Palo Alto PAN-OS Management Web Authentication Bypass (3)" (Authentication/Authorization Attacks, risk High), systems: PHP, Other Web Server, Proxy Servers. References: CVE-2025-0108.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.