CVE-2026-75583

LOWPre-NVD 3.53.5
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 3.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-62585 (ENISA EUVD)Source: ENISA EUVD

3.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

keeper.sh's calendar module version prior to 2.18.14 contains a server-side request forgery (SSRF) guard bypass vulnerability that allows authenticated attackers to reach private network addresses by exploiting a DNS rebinding attack against the two-phase URL validation and connection flow. The SSRF guard validates a hostname's resolved IP addresses but discards them before the actual HTTP connection is opened, allowing an attacker who controls authoritative DNS to return a public address during validation and a private address during the subsequent independent socket-level DNS resolution, causing the guard to pass while the outbound connection reaches internal infrastructure such as cloud instance metadata endpoints.

CVSS v3
3.5
EG Score
3.5LOWmedium confidence
EG Risk
16
EG Risk 16/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)
Severity35% × 45%
Impact severity (EG Severity): CVSS 3.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.3%
EPSS %ILE
25th
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 (3.5): severity, escalated by confirmed exploitation. This CVE's 3.5 is its impact severity (EG Severity), not escalated.

EG Severity
3.5 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

August 19, 2026

Last Modified

September 24, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× 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 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.

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 93 are merged into the row they repeat.

  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-29 17:22 UTCEG score recompute
  3. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-27 01:55 UTCOSV refresh
  7. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-25 14:02 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-10-18 03:13 UTCEG score recompute
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-10-12 15:39 UTCEG score recompute
  25. 2026-10-11 19:24 UTCEG score recompute
Show 66 more
  1. 2026-10-11 16:40 UTCEG score recompute
  2. 2026-10-11 13:59 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-06 07:58 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-03 07:06 UTCEG score recompute
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-09-30 11:56 UTCEG score recompute
  16. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-09-27 16:10 UTCEG score recompute
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-09-24 20:15 UTCEG score recompute
  23. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-09-23 20:09 UTCEG score recompute
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-21 01:54 UTCEG score recompute
  29. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-18 07:39 UTCEG score recompute
  32. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-09-15 13:24 UTCEG score recompute
  35. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-09-12 19:09 UTCEG score recompute
  37. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  39. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-09-10 00:54 UTCEG score recompute
  41. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-09-07 01:34 UTCEG score recompute
  43. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  44. 2026-09-04 07:16 UTCEG score recompute
  45. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  46. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  47. 2026-09-01 12:55 UTCEG score recompute
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-29 18:16 UTCEG score recompute
  52. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-27 00:00 UTCEG score recompute
  55. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-24 05:45 UTCEG score recompute
  59. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-21 11:30 UTCEG score recompute
  62. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  63. 2026-08-19 18:29 UTCEG score recompute
  64. 2026-08-19 17:28 UTCEG score recompute
  65. 2026-08-19 16:43 UTCEG score recomputeFirst assessed: 3.5 LOW
  66. 2026-08-19 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75583?
CVE-2026-75583 is a low-severity vulnerability; its CVE record was published on August 19, 2026. keeper.sh's calendar module version prior to 2.18.14 contains a server-side request forgery (SSRF) guard bypass vulnerability that allows authenticated attackers to reach private network addresses by exploiting a DNS rebinding attack against the two-phase URL validation and connection flow. The…
When was CVE-2026-75583 made public?
CVE-2026-75583 was made public on August 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-75583 actively exploited?
CVE-2026-75583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75583?
CVE-2026-75583 has a CVSS base score of 3.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75583?
A fix for CVE-2026-75583 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-75583?

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