CVE-2025-0114
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Denial of Service (DoS) vulnerability in the GlobalProtect feature of Palo Alto Networks PAN-OS software enables an unauthenticated attacker to render the service unavailable by sending a large number of specially crafted packets over a period of time. This issue affects both the GlobalProtect portal and the GlobalProtect gateway. This issue does not apply to Cloud NGFWs or Prisma Access software.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Denial of Service vulnerability in Palo Alto Networks PAN-OS GlobalProtect feature allows an unauthenticated attacker to render the service unavailable by sending a large number of specially crafted packets over time. The attack targets both GlobalProtect portal and GlobalProtect gateway, exploiting the service's handling of crafted network traffic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.1.0, < 10.1.14>= 10.2.0, < 10.2.5>= 11.0.0, < 11.0.2= 10.1.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check PAN-OS versionRun 'show system info' or access the PAN-OS web interface under Device > Setup > Operations to view the installed PAN-OS versionAffected if The installed version is >= 10.1.0 and < 10.1.14, OR >= 10.2.0 and < 10.2.5, OR >= 11.0.0 and < 11.0.2, OR equals exactly 10.1.14
-
Verify GlobalProtect is enabledCheck Network > GlobalProtect > Portals and Network > GlobalProtect > Gateways to see if any GlobalProtect configurations existAffected if Any GlobalProtect portal or gateway is configured and enabled on the device
-
Confirm GlobalProtect interface exposureReview the interface assignments under Network > GlobalProtect > Portals and Network > GlobalProtect > Gateways to identify which interfaces accept GlobalProtect trafficAffected if GlobalProtect is bound to external or untrusted interfaces accessible from the network
-
Check for service availabilityAttempt to access the GlobalProtect portal URL or ping the GlobalProtect gateway interface to verify the service is respondingAffected if The service is unreachable or responding intermittently after receiving crafted network traffic
A user is affected if their PAN-OS version falls within the affected ranges AND GlobalProtect portal or gateway is enabled and exposed on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.1.1410.2.511.0.2
Apply the vendor-supplied patch for PAN-OS when available, or implement network-level rate limiting and traffic filtering for GlobalProtect interfaces to mitigate the attack vector until patching can be completed.
PAN-OS 10.1.14-h2+ / 10.1.15+, 10.2.5+, or 11.0.2+ (based on current branch)
- 1. Identify the current PAN-OS version by navigating to Device > Dynamic Updates in the web interface or using 'show system info' in CLI
- 2. For PAN-OS 10.1.x: Upgrade to PAN-OS 10.1.14-h2 or later (or 10.1.15+)
- 3. For PAN-OS 10.2.x: Upgrade to PAN-OS 10.2.5 or later
- 4. For PAN-OS 11.0.x: Upgrade to PAN-OS 11.0.2 or later
- 5. Download the latest content and software updates from the Palo Alto Networks Support Portal
- 6. Schedule a maintenance window and backup the current configuration
- 7. Upload and install the new PAN-OS version following standard upgrade procedures
- 8. After reboot, verify the GlobalProtect service is operational and the version is correct using 'show system info'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0114 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data