vciy

CVE-2022-0024

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

PAN-OS: Improper Neutralization Vulnerability Leads to Unintended Program Execution During Configuration Commit

CVE-2022-00244 of 4 sources documented this
24

rank 24 = 0 + 18 + 0 + 6 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.01607  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.2, from NVD  ·  without this subject the record ranks 6

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 24

How much of the world it touches

NVD CPE configurations

5 products in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Hindsight · the state

0.01607EPSSNOT IN KEVas of 2026-10-18
Severity7.2 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementfallenreceipt
PLATEAU10Minimal movement since 2022-05-12, 1602 days at 0.02, as of 2026-09-30. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Palo Alto Networks PAN-OS? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch Palo Alto Networks PAN-OS

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · high privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-138 Improper Neutralization of Special Elementsreceipt
Published consequencesCWE-138: Confidentiality, Integrity, Availability, Other: Execute Unauthorized Code or Commands, Alter Execution Logic, DoS: Crash, Exit, or Restartcwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in9.1.13; 10.1.5; 9.0.16; 8.1.23; 10.0.10receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.2 HIGHreceipt
CVSS, NVD7.2 HIGHreceipt
Exploit probability0.01607 · top 25% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bypalo_altoreceipt
Recorded changes34 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productPalo Alto Networks PAN-OSreceipt
Published rangespaloaltonetworks pan-os >= 8.1.0 < 8.1.23; paloaltonetworks pan-os >= 9.0.0 < 9.0.16; paloaltonetworks pan-os >= 9.1.0 < 9.1.13; paloaltonetworks pan-os >= 10.0.0 < 10.0.10receipt
Show all 5 published ranges
paloaltonetworks pan-os >= 8.1.0 < 8.1.23
paloaltonetworks pan-os >= 9.0.0 < 9.0.16
paloaltonetworks pan-os >= 9.1.0 < 9.1.13
paloaltonetworks pan-os >= 10.0.0 < 10.0.10
paloaltonetworks pan-os >= 10.1.0 < 10.1.5
Fixed in9.1.13; 10.1.5; 9.0.16; 8.1.23; 10.0.10receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$80,200over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$80,200 = $4.99M incident cost x 1 exposure x 0.01607 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires high privilegesPalo Alto Networks PAN-OSCWE-138 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-138data compromise

What it is stated by the CNA

A vulnerability exists in Palo Alto Networks PAN-OS software that enables an authenticated network-based PAN-OS administrator to upload a specifically created configuration that disrupts system processes and potentially execute arbitrary code with root privileges when the configuration is committed on both hardware and virtual firewalls. This issue does not impact Panorama appliances or Prisma Access customers. This issue impacts: PAN-OS 8.1 versions earlier than PAN-OS 8.1.23; PAN-OS 9.0 versions earlier than PAN-OS 9.0.16; PAN-OS 9.1 versions earlier than PAN-OS 9.1.13; PAN-OS 10.0 versions earlier than PAN-OS 10.0.10; PAN-OS 10.1 versions earlier than PAN-OS 10.1.5. receipt

NVD's analysis a second authority

severity
7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-138
affected versions
paloaltonetworks pan-os >= 8.1.0 < 8.1.23; paloaltonetworks pan-os >= 9.0.0 < 9.0.16; paloaltonetworks pan-os >= 9.1.0 < 9.1.13; and 2 more, listed in full below
also scored by
psirt@paloaltonetworks.com 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

check it yourself security.paloaltonetworks.com receipt

Movement the material steps

12 May 20220.02559
7 Mar 20235.5e-4 · scoring model v2023.03.01
17 Mar 20250.01015 · scoring model v2025.03.14
15 Jun 20260.01398 · scoring model v2026.06.15
30 Sep 20260.01607
Show all 34 observations
12 May 20220.02559
21 May 20220.01086
7 Mar 20235.5e-4
8 Mar 20230.00055
18 Mar 20230.00056
11 Apr 20230.00065
18 May 20230.00100
22 Oct 20230.00105
17 Mar 20250.01015
29 Mar 20250.01598
30 Mar 20250.01015
12 May 20250.00749
29 May 20250.00869
30 Jul 20250.00718
2 Sep 20250.00754
7 Sep 20250.00833
11 Sep 20250.00887
29 Sep 20250.01001
1 Oct 20250.0121
18 Oct 20250.01368
27 Oct 20250.01255
28 Oct 20250.01516
18 Nov 20250.01316
21 Nov 20250.01516
23 Nov 20250.01365
18 Dec 20250.01357
27 Dec 20250.01123
28 Dec 20250.01316
22 May 20260.01777
15 Jun 20260.01398
5 Jul 20260.01467
28 Jul 20260.0151
9 Sep 20260.01547
30 Sep 20260.01607

34 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.01607Published2022-05-11Index as of2026-09-30

The record had been public for 4 years, 4 months when this index was last written.

Published 2022-05-11 receipt · Index as of 2026-09-30 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2022-0024.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.