CVSS 4.0
7.8 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N/E:A/AU:N/R:A/V:D/RE:M/U:RedHigh (7.8) in Palo Alto Networks PAN-OS. In CISA KEV since 2026-05-29, with known ransomware use. EPSS 96% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N/E:A/AU:N/R:A/V:D/RE:M/U:RedCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExplain CVE-2026-0257 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0257?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0257?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-0257 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Palo Alto Networks PAN-OS | from 12.1.0 before 12.1.7, 12.1.4-h6 |
| Palo Alto Networks PAN-OS | from 11.2.0 before 11.2.12, 11.2.10-h7, 11.2.7-h14, 11.2.4-h17 |
| Palo Alto Networks PAN-OS | from 11.1.0 before 11.1.15, 11.1.13-h5, 11.1.10-h25, 11.1.7-h6, 11.1.6-h32, 11.1.4- |
| Palo Alto Networks PAN-OS | from 10.2.0 before 10.2.18-h6, 10.2.16-h7, 10.2.13-h21, 10.2.10-h36, 10.2.7-h34 |
| Palo Alto Networks Prisma Access | from 10.2.0 before 10.2.10-h36 |
| Palo Alto Networks Prisma Access | from 11.2.0 before 11.2.7-h13 |
| Product | Fixed in |
|---|---|
| Palo Alto Networks PAN-OS | 12.1.7 |
| Palo Alto Networks PAN-OS | 12.1.4-h6 |
| Palo Alto Networks PAN-OS | 11.2.12 |
| Palo Alto Networks PAN-OS | 11.2.10-h7 |
| Palo Alto Networks PAN-OS | 11.2.7-h14 |
| Palo Alto Networks PAN-OS | 11.2.4-h17 |
| Palo Alto Networks PAN-OS | 11.1.15 |
| Palo Alto Networks PAN-OS | 11.1.13-h5 |
| Palo Alto Networks PAN-OS | 11.1.10-h25 |
| Palo Alto Networks PAN-OS | 11.1.7-h6 |
| Palo Alto Networks PAN-OS | 11.1.6-h32 |
| Palo Alto Networks PAN-OS | 11.1.4-h33 |
| Palo Alto Networks PAN-OS | 10.2.18-h6 |
| Palo Alto Networks PAN-OS | 10.2.16-h7 |
| Palo Alto Networks PAN-OS | 10.2.13-h21 |
| Palo Alto Networks PAN-OS | 10.2.10-h36 |
| Palo Alto Networks PAN-OS | 10.2.7-h34 |
| Palo Alto Networks Prisma Access | 10.2.10-h36 |
| Palo Alto Networks Prisma Access | 11.2.7-h13 |
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-26-139-02 | Siemens RUGGEDCOM APE1808 Devices | 2026-05-12 | Critical Manufacturing | RUGGEDCOM APE1808 | none listed |
From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.