CVE-2026-33267

CRITICALNVD 9.110.0
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. NVD baseline CVSS 9.1; sources differ by 0.9.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: Public PoCExposed services: Not assessed

The CVE record names the fixed release — apply it.

Improper Input Validation vulnerability in Apache Traffic Server.

This issue affects Apache Traffic Server: from 9.2.0 through 9.2.14, from 10.1.0 through 10.1.3.

Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fixes the issue.

CVSS v3
9.1
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 29, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
Fix named in the CVE record.

Vendor Advisories for CVE-2026-33267(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
trafficserver8.1.1+ds-1.1 ... 9.2.5+ds-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
trafficserver9.2.0+ds-2 ... 9.2.5+ds-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 89× 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 99 of 399 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 300 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCBoreas37/CVE-2026-33267-PoC
    Published Aug 12, 2026

    CVE-2026-33267 — Apache Traffic Server @ header internal-metadata spoof (CVSS 10.0). Verified: @ headers leak to plugins on 10.1.2, stripped on 10.1.4

    Open source ↗

Frequently asked(5)

What is CVE-2026-33267?
CVE-2026-33267 is a critical-severity vulnerability; its CVE record was published on July 29, 2026. Improper Input Validation vulnerability in Apache Traffic Server. This issue affects Apache Traffic Server: from 9.2.0 through 9.2.14, from 10.1.0 through 10.1.3. Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fixes the issue.
When was the CVE record for CVE-2026-33267 published?
The CVE record for CVE-2026-33267 was published on July 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-33267 actively exploited?
CVE-2026-33267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33267?
CVE-2026-33267 has a CVSS v3 base score of 9.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2026-33267?
The CVE record for CVE-2026-33267 names the fix: "Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-33267 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-33267

Explore →

Is Your Infrastructure Affected by CVE-2026-33267?

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