# CVE-2025-0136: PAN-OS: Unencrypted Data Transfer when using AES-128-CCM on Intel-based hardware devices

> Attackers can read sensitive data in transit when AES-128-CCM is used for IPSec on specific Intel-based PAN-OS firewalls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:C/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2025
- **Updated:** 14 May 2025
- **Also known as:** GHSA-9wg5-mqr8-x4m3

## What is CVE-2025-0136?

CVE-2025-0136 is a medium-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 14 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Using the AES-128-CCM algorithm for IPSec on certain Palo Alto Networks PAN-OS® firewalls (PA-7500, PA-5400, PA-5400f, PA-3400, PA-1600, PA-1400, and PA-400 Series) leads to unencrypted data transfer to devices that are connected to the PAN-OS firewall through IPSec.

This issue does not affect Cloud NGFWs, Prisma® Access instances, or  PAN-OS VM-Series firewalls.

NOTE: The AES-128-CCM encryption algorithm is not recommended for use.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2025-0136?


## How do I fix CVE-2025-0136?

No fix has been published for CVE-2025-0136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0136 being exploited?

There is no known exploitation of CVE-2025-0136 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0136 and fix it if it is affected.

What it is: CVE-2025-0136 is a medium-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 14 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0136 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cloud NGFW. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0136/ (Markdown: https://insights.sbomify.com/CVE-2025-0136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0136
- OSV: https://osv.dev/vulnerability/CVE-2025-0136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0136/
Summaries are generated and may contain mistakes; the official description above is the record.