CVE-2026-73501

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

kin-openapi is a Go project for handling OpenAPI files. Prior to 0.144.0, ValidationHandler.Load() in openapi3filter/validation_handler.go silently replaces a nil AuthenticationFunc with NoopAuthenticationFunc, which returns nil without checking credentials. This substitution causes every OpenAPI security requirement to be satisfied for unauthenticated requests when an application relies on ValidationHandler as its enforcement middleware. The no-op callback prevents the fail-closed ErrAuthenticationServiceMissing path from being reached and forwards the request to protected handlers that may require an API key, OAuth token, or another security scheme. This issue is fixed in version 0.144.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 12, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

ValidationHandler.Load() Fail-Open Authentication Bypass via NoopAuthenticationFunc Default · Advisory · getkin/kin-openapi · GitHub

https://github.com/getkin/kin-openapi/security/advisories/GHSA-r277-6w6q-xmqw
github_release Patch Available

v0.144.0

Patch available: getkin/kin-openapi v0.144.0

https://github.com/getkin/kin-openapi/releases/tag/v0.144.0
github_commit Patch Available

commit f0407d53b073 (getkin/kin-openapi)

Patch available: getkin/kin-openapi v0.144.0 (contains commit f0407d53b073)

https://github.com/getkin/kin-openapi/commit/f0407d53b0730280266f454b755010e7eeb985da

Vendor Advisories for CVE-2026-73501(4)

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 / EcosystemFixed in / PatchReleasedSource
redhatgrafana12-4-main-12.4.9-0.4.hum12026-08-29redhat
redhatgrafana13-1-main-13.1.3-0.2.hum12026-08-24redhat
redhatgrafana13-2-main-13.2.0-0.1.1.hum12026-08-24redhat
redhathugo-main-0.165.0-0.1.hum12026-08-13redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-getkin-kin-openapi0.110.0-1 ... 0.135.0-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-getkin-kin-openapi0.124.0-1, 0.135.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-getkin-kin-openapi0.124.0-1, 0.135.0-1——
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/getkin/kin-openapi—0.144.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 50× in last 7d / 163× 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 185 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73501?
CVE-2026-73501 is a critical vulnerability published on August 12, 2026. kin-openapi is a Go project for handling OpenAPI files. Prior to 0.144.0, ValidationHandler.Load() in openapi3filter/validation_handler.go silently replaces a nil AuthenticationFunc with NoopAuthenticationFunc, which returns nil without checking credentials. This substitution causes every OpenAPI…
When was CVE-2026-73501 disclosed?
CVE-2026-73501 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73501 actively exploited?
CVE-2026-73501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73501?
CVE-2026-73501 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-73501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73501, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73501?

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

Start Free Scan →Browse All CVEs