CVE-2022-36227

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-11-22. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In libarchive before 3.6.2, the software does not check for an error after calling calloc function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference. NOTE: the discoverer cites this CWE-476 remark but third parties dispute the code-execution impact: "In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution."

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
78%
KEV
Not listed

Published

November 22, 2022

Last Modified

November 3, 2025

Advisory Details (6)

Auto-updated Jul 28, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 3294-1] libarchive security update

https://lists.debian.org/debian-lts-announce/2023/01/msg00034.html
generic

There is a NULL pointer dereference vulnerability · Issue #1754 · libarchive/libarchive · GitHub

https://github.com/libarchive/libarchive/issues/1754
generic

libarchive/libarchive/archive_write.c at v3.0.0a · libarchive/libarchive · GitHub

https://github.com/libarchive/libarchive/blob/v3.0.0a/libarchive/archive_write.c#L215
generic

882521 – (CVE-2022-36227) <app-arch/libarchive-3.6.1-r1: null pointer dereference

https://bugs.gentoo.org/882521
generic

libarchive: Multiple Vulnerabilities (GLSA 202309-14) — Gentoo security

https://security.gentoo.org/glsa/202309-14
generic

[SECURITY] Fedora 37 Update: libarchive-3.6.1-3.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V67OO2UUQAUJS3IK4JZPF6F3LUCBU6IS/

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibarchive13 (3.4.0-2ubuntu1.3) @ focal2026-05-25ubuntu
redhatlibarchive-0:3.3.3-4.el8_62024-01-10redhat
redhatlibarchive-0:3.3.3-5.el82023-05-16redhat
redhatlibarchive-0:3.5.3-4.el92023-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 115 total refreshes for this CVE.

  1. 2026-07-26 14:52 UTCEPSS rescore
  2. 2026-07-25 14:15 UTCEPSS rescore
  3. 2026-07-25 14:15 UTCEPSS rescore
  4. 2026-07-24 14:15 UTCEPSS rescore
  5. 2026-07-24 14:15 UTCEPSS rescore
  6. 2026-07-23 14:16 UTCEPSS rescore
  7. 2026-07-23 02:12 UTCEG score recompute
  8. 2026-07-22 22:59 UTCEG score recompute
  9. 2026-07-22 14:06 UTCEPSS rescore
  10. 2026-07-22 14:06 UTCEPSS rescore
  11. 2026-07-21 15:23 UTCEPSS rescore
  12. 2026-07-21 15:22 UTCEPSS rescore
  13. 2026-07-20 17:05 UTCEPSS rescore
  14. 2026-07-19 14:29 UTCEPSS rescore
  15. 2026-07-19 02:27 UTCEPSS rescore
  16. 2026-07-19 02:27 UTCEPSS rescore
  17. 2026-07-18 10:03 UTCEPSS rescore
  18. 2026-07-18 10:03 UTCEPSS rescore
  19. 2026-07-16 17:00 UTCEPSS rescore
  20. 2026-07-16 14:23 UTCOSV refresh
  21. 2026-07-15 16:56 UTCEPSS rescore
  22. 2026-07-15 16:56 UTCEPSS rescore
  23. 2026-07-15 01:58 UTCEPSS rescore
  24. 2026-07-15 01:58 UTCEPSS rescore
  25. 2026-07-13 22:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-13 22:28 UTCEPSS rescore
  2. 2026-07-12 05:44 UTCEPSS rescore
  3. 2026-07-12 05:44 UTCEPSS rescore
  4. 2026-07-11 08:25 UTCEPSS rescore
  5. 2026-07-09 19:08 UTCEPSS rescore
  6. 2026-07-08 15:12 UTCEPSS rescore
  7. 2026-07-07 13:44 UTCEPSS rescore
  8. 2026-07-06 16:25 UTCEPSS rescore
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-07-06 02:21 UTCEPSS rescore
  11. 2026-07-06 02:21 UTCEPSS rescore
  12. 2026-07-05 02:28 UTCEPSS rescore
  13. 2026-07-04 06:29 UTCEPSS rescore
  14. 2026-07-04 06:29 UTCEPSS rescore
  15. 2026-07-01 15:04 UTCEPSS rescore
  16. 2026-06-30 23:20 UTCEPSS rescore
  17. 2026-06-30 23:20 UTCEPSS rescore
  18. 2026-06-29 14:04 UTCEPSS rescore
  19. 2026-06-28 14:06 UTCEPSS rescore
  20. 2026-06-28 13:19 UTCOSV refresh
  21. 2026-06-28 04:54 UTCEPSS rescore
  22. 2026-06-28 04:54 UTCEPSS rescore
  23. 2026-06-27 03:07 UTCEPSS rescore
  24. 2026-06-27 03:07 UTCEPSS rescore
  25. 2026-06-25 13:48 UTCEPSS rescore
  26. 2026-06-25 13:48 UTCEPSS rescore
  27. 2026-06-24 14:03 UTCEPSS rescore
  28. 2026-06-24 14:03 UTCEPSS rescore
  29. 2026-06-23 21:31 UTCEPSS rescore
  30. 2026-06-23 21:31 UTCEPSS rescore
  31. 2026-06-22 14:24 UTCEPSS rescore
  32. 2026-06-22 14:24 UTCEPSS rescore
  33. 2026-06-21 14:55 UTCEPSS rescore
  34. 2026-06-21 14:55 UTCEPSS rescore
  35. 2026-06-21 01:58 UTCEPSS rescore
  36. 2026-06-21 01:58 UTCEPSS rescore
  37. 2026-06-19 19:24 UTCEPSS rescore
  38. 2026-06-19 19:24 UTCEPSS rescore
  39. 2026-06-18 17:51 UTCEPSS rescore
  40. 2026-06-18 17:51 UTCEPSS rescore
  41. 2026-06-17 17:51 UTCEPSS rescore
  42. 2026-06-17 17:51 UTCEPSS rescore
  43. 2026-06-16 17:51 UTCEPSS rescore
  44. 2026-06-15 17:46 UTCEPSS rescore
  45. 2026-06-14 23:15 UTCEPSS rescore
  46. 2026-06-13 22:58 UTCEPSS rescore
  47. 2026-06-12 23:10 UTCEPSS rescore
  48. 2026-06-12 23:10 UTCEPSS rescore
  49. 2026-06-11 13:58 UTCEPSS rescore
  50. 2026-06-11 13:58 UTCEPSS rescore
  51. 2026-06-11 00:09 UTCOSV refresh
  52. 2026-06-10 22:17 UTCEPSS rescore
  53. 2026-06-10 13:20 UTCEPSS rescore
  54. 2026-06-08 14:15 UTCEPSS rescore
  55. 2026-06-08 14:15 UTCEPSS rescore
  56. 2026-06-07 15:23 UTCEPSS rescore
  57. 2026-06-07 15:23 UTCEPSS rescore
  58. 2026-06-06 13:46 UTCEPSS rescore
  59. 2026-06-06 13:46 UTCEPSS rescore
  60. 2026-06-06 13:46 UTCEPSS rescore
  61. 2026-06-05 22:46 UTCEPSS rescore
  62. 2026-06-05 22:45 UTCEPSS rescore
  63. 2026-06-05 06:09 UTCEPSS rescore
  64. 2026-06-05 06:09 UTCEPSS rescore
  65. 2026-06-04 13:11 UTCEPSS rescore
  66. 2026-06-04 13:11 UTCEPSS rescore
  67. 2026-06-02 20:11 UTCEPSS rescore
  68. 2026-06-02 20:11 UTCEPSS rescore
  69. 2026-06-01 13:50 UTCEPSS rescore
  70. 2026-06-01 13:50 UTCEPSS rescore
  71. 2026-05-31 22:29 UTCEPSS rescore
  72. 2026-05-31 22:29 UTCEPSS rescore
  73. 2026-05-31 22:29 UTCEPSS rescore
  74. 2026-05-31 00:15 UTCEPSS rescore
  75. 2026-05-31 00:15 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-36227?
CVE-2022-36227 is a critical vulnerability published on November 22, 2022. In libarchive before 3.6.2, the software does not check for an error after calling calloc function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference. NOTE: the discoverer cites this CWE-476 remark but third parties dispute the…
When was CVE-2022-36227 disclosed?
CVE-2022-36227 was first published in the National Vulnerability Database on November 22, 2022, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-36227 actively exploited?
CVE-2022-36227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 22.1% of all scored CVEs.
What is the CVSS score of CVE-2022-36227?
CVE-2022-36227 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-36227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-36227, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-36227

Explore →

Is Your Infrastructure Affected by CVE-2022-36227?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs