CVE-2026-78367

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Red Hat, Inc.) lists Red Hat Hardened Images versions 6.1.0-1.3.hum1 and later as unaffected. No release containing a fix is confirmed on record.

A vulnerability was found in RPM's rpmbuild tarball processing. When processing a crafted source archive, the getTarSpec() function in tools/rpmbuild.cc passes an attacker-controlled tar archive member name to rpmExpand() as part of a %{basename:...} macro expression. A specially crafted .spec member name can therefore inject RPM macros, including Lua expressions, resulting in arbitrary code execution with the privileges of the user running rpmbuild. This can be exploited when a victim or automated build system processes an attacker-controlled source tarball using rpmbuild tarball mode (such as -ts, -ta, or -tb).

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
48
EG Risk 48/100

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 (value × EchelonGraph’s weight)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 14, 2026

Advisory Details (3)

Auto-updated Aug 24, 2026
No fix on record yet. Sources: redhat.
Web page

rpmbuild getTarSpec() — crafted tar member name → macro injection · Issue #4314 · rpm-software-management/rpm · GitHub

https://github.com/rpm-software-management/rpm/issues/4314
Red Hat

2521857 – (CVE-2026-78367) CVE-2026-78367 rpm: rpmbuild getTarSpec() crafted tar member name → macro injection

https://bugzilla.redhat.com/show_bug.cgi?id=2521857
Red HatMentions a patch (unverified)

CVE-2026-78367 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-78367

Vendor Advisories for CVE-2026-78367(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rpm4.18.0+dfsg-1 ... 6.1.0-1 (20 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rpm4.20.1+dfsg-3, 6.0.0-1, 6.0.0-2, 6.0.1-1, 6.1.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rpm4.20.1+dfsg-3, 6.0.0-1, 6.0.0-2, 6.0.1-1, 6.1.0-1
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 110× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 203 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-78367?
CVE-2026-78367 is a high-severity vulnerability; its CVE record was published on August 24, 2026. A vulnerability was found in RPM's rpmbuild tarball processing. When processing a crafted source archive, the getTarSpec() function in tools/rpmbuild.cc passes an attacker-controlled tar archive member name to rpmExpand() as part of a %{basename:...} macro expression. A specially crafted .spec…
When was CVE-2026-78367 made public?
CVE-2026-78367 was made public on August 24, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-78367 actively exploited?
CVE-2026-78367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78367?
CVE-2026-78367 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78367?
No fix for CVE-2026-78367 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Red Hat, Inc.) lists Red Hat Hardened Images versions 6.1.0-1.3.hum1 and later as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-78367 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78367

Explore →

Is Your Infrastructure Affected by CVE-2026-78367?

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

Book a Demo →Browse All CVEs