CVE-2026-30633

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Elevated
7.5EG
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.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Directory traversal vulnerability in knowns-dev/knowns 0.11.4 via crafted path value to the get_doc and update_doc tools.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
The EG Score, 7.5 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 public PoC (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: An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.

Exploitation public PoC (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.

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

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

knowns_get_update_doc_poc.md · GitHub

https://gist.github.com/spdc-elm/5e19d66402307bdfc8b25ab27469172f
GitHub commit

commit 62fb0daaa0b9 (knowns-dev/knowns)

Fix landed in knowns-dev/knowns commit 62fb0daaa0b9 — awaiting tagged release

https://github.com/knowns-dev/knowns/commit/62fb0daaa0b9e66fce1d42c02b5bb519367cf669

Vendor Advisories for CVE-2026-30633(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 96 of 225 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-30633?
CVE-2026-30633 is a high-severity vulnerability; its CVE record was published on July 21, 2026. Directory traversal vulnerability in knowns-dev/knowns 0.11.4 via crafted path value to the getdoc and updatedoc tools.
When was the CVE record for CVE-2026-30633 published?
The CVE record for CVE-2026-30633 was published on July 21, 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-30633 actively exploited?
CVE-2026-30633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-30633?
CVE-2026-30633 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-30633?
An upstream fix for CVE-2026-30633 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-30633 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-30633

Explore →

Is Your Infrastructure Affected by CVE-2026-30633?

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