CVE-2022-24761

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-03-18. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-0358 (ENISA EUVD) · GHSA-4f7p-27jc-3c36 (GitHub Security Advisories) · PYSEC-2022-169 (OSV.dev)Source: ENISA EUVD

7.5EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python's int() to parse strings into integers, leading to +10 to be parsed as 10, or 0x01 to be parsed as 1, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 partial (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.8%
EPSS %ILE
78th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. 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 partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

March 17, 2022

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Nov 13, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

[SECURITY] [DSA 5138-1] waitress security update

https://www.debian.org/security/2022/dsa-5138
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3000-1] waitress security update

https://lists.debian.org/debian-lts-announce/2022/05/msg00011.html
GitHub advisoryMentions a patch (unverified)

Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') in waitress · Advisory · Pylons/waitress · GitHub

https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36
GitHub release Patch Available

v2.1.1

Patch available: Pylons/waitress v2.1.1

https://github.com/Pylons/waitress/releases/tag/v2.1.1
GitHub commit Patch Available

commit 9e0b8c801e4d (Pylons/waitress)

Patch available: Pylons/waitress v2.1.1 (contains commit 9e0b8c801e4d)

https://github.com/Pylons/waitress/commit/9e0b8c801e4d505c2ffc91b891af4ba48af715e0

Vendor Advisories for CVE-2022-24761(2)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-waitress (1.4.4-1.1ubuntu0.1) @ impish2026-10-29ubuntu
redhatpython-waitress-0:1.4.4-2.el7ost2022-04-07redhat
redhatpython-waitress-0:2.0.0-1.el8ost2022-04-06redhat
pipwaitress @ 2.1.1 (fixes < 2.1.1)—ghsa

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.

Affected Packages

(7 across 7 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
waitress1.2.0~b2-2
  • every version up to 1.2.0~b2-2+deb10u1: fixed in 1.2.0~b2-2+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
waitress1.4.4-1.1
  • every version up to 1.4.4-1.1+deb11u1: fixed in 1.4.4-1.1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
waitress—
  • every version up to 2.1.1-1: fixed in 2.1.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
waitress—
  • every version up to 2.1.1-1: fixed in 2.1.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
waitress—
  • every version up to 2.1.1-1: fixed in 2.1.1-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
waitress1.0.1-1
  • every version up to 1.0.1-1+deb9u1: fixed in 1.0.1-1+deb9u1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
waitress0.1 ... 2.1.0b0 (47 versions)
  • every version up to 2.1.1: fixed in 2.1.1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 224 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:41 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  2. 2026-11-13 06:21 UTCEchelonGraph re-scored
  3. 2026-11-13 06:21 UTCVendor advisory
  4. 2026-11-13 06:21 UTCGHSA enrichmentGHSA-4f7p-27jc-3c36 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-12 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  6. 2026-11-11 16:32 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  7. 2026-11-10 16:35 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  8. 2026-11-09 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  9. 2026-11-08 16:33 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  10. 2026-11-07 16:34 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  11. 2026-11-06 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  12. 2026-11-05 16:46 UTCEchelonGraph re-scored
  13. 2026-11-05 16:46 UTCVendor advisory
  14. 2026-11-05 16:46 UTCGHSA enrichmentGHSA-4f7p-27jc-3c36 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-05 16:31 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  16. 2026-11-04 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  17. 2026-11-03 16:39 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  18. 2026-11-02 16:38 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  19. 2026-11-01 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  20. 2026-11-01 08:28 UTCGHSA enrichmentGHSA-4f7p-27jc-3c36 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 08:28 UTCEchelonGraph re-scored
  22. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  23. 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  24. 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  25. 2026-10-29 03:06 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-10-29 03:06 UTCVendor advisory
  2. 2026-10-29 01:55 UTCOSV refresh
  3. 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  4. 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  5. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  6. 2026-10-25 18:12 UTCEchelonGraph re-scored
  7. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  8. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  9. 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  10. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  11. 2026-10-21 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  12. 2026-10-21 07:49 UTCEchelonGraph re-scored
  13. 2026-10-21 07:49 UTCVendor advisory
  14. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  15. 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  16. 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  17. 2026-10-18 08:41 UTCEchelonGraph re-scored
  18. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  19. 2026-10-17 00:55 UTCOSV refresh
  20. 2026-10-16 16:34 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  21. 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  22. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  23. 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  24. 2026-10-12 18:58 UTCEchelonGraph re-scored
  25. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  26. 2026-10-11 23:24 UTCEchelonGraph re-scored
  27. 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  28. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  29. 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  30. 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  31. 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  32. 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  33. 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  34. 2026-10-04 23:19 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  35. 2026-10-03 14:22 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  36. 2026-09-30 15:51 UTCEchelonGraph re-scored
  37. 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  38. 2026-09-29 15:15 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  39. 2026-09-28 13:48 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  40. 2026-09-27 13:41 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  41. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  42. 2026-09-25 02:54 UTCOSV refresh
  43. 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  44. 2026-09-23 13:45 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  45. 2026-09-17 19:23 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  46. 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  47. 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  48. 2026-09-13 16:43 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  49. 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  50. 2026-09-11 14:49 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  51. 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  52. 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  53. 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  54. 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  55. 2026-09-05 18:25 UTCOSV refresh
  56. 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  57. 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  58. 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  59. 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  60. 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  61. 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  62. 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  63. 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  64. 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  65. 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  66. 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  67. 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  68. 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  69. 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  70. 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  71. 2026-08-19 05:02 UTCOSV refresh
  72. 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.8% · 76th percentile
  73. 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.8% · 76th percentile

Frequently asked(5)

What is CVE-2022-24761?
CVE-2022-24761 is a high-severity vulnerability; its CVE record was published on March 17, 2022. Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and…
When was the CVE record for CVE-2022-24761 published?
The CVE record for CVE-2022-24761 was published on March 17, 2022. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-24761 actively exploited?
CVE-2022-24761 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24761?
CVE-2022-24761 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-24761?
A fix for CVE-2022-24761 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-24761 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-2022-24761

Explore →

Is Your Infrastructure Affected by CVE-2022-24761?

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