CVE-2026-75608

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th 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
Elevated

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

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Frigate is an open source network video recorder. Prior to 0.18.0, the prefix-matched location /api/go2rtc/api in docker/main/rootfs/usr/local/nginx/conf/nginx.conf requires authentication but does not require an administrator role for GET requests, exposing the proxied go2rtc API to viewer users. An authenticated viewer can request the streams, config, log, and stack subpaths to obtain internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials. Non-GET methods remain blocked by limit_except GET. This issue is fixed in version 0.18.0.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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 available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
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.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Track* at high (mission-essential systems).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, 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

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

The score's inputs: 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

September 22, 2026

Last Modified

September 28, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

0.18.0 Release

Patch available: blakeblackshear/frigate v0.18.0

https://github.com/blakeblackshear/frigate/releases/tag/v0.18.0
GitHub commit

commit 520d9eeb7f0f (blakeblackshear/frigate)

Fix landed in blakeblackshear/frigate commit 520d9eeb7f0f — awaiting tagged release

https://github.com/blakeblackshear/frigate/commit/520d9eeb7f0fe46021f29fb8169741dd1d429271
GitHub pull request

Remove direct go2rtc API proxy in favor of frigate API endpoints

Fix merged in blakeblackshear/frigate PR #22735 on 2026-04-02 — awaiting tagged release

https://github.com/blakeblackshear/frigate/pull/22735
GitHub advisoryMentions a patch (unverified)

Viewer-Role User Can Access go2rtc Internal API to obtain sensitive information · Advisory · blakeblackshear/frigate · GitHub

https://github.com/blakeblackshear/frigate/security/advisories/GHSA-mgh5-cr9h-g6hr

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× 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.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-27 19:43 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-25 14:02 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-20 08:20 UTCEG score recompute
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-18 03:13 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-13 07:20 UTCEG score recompute
Show 45 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-12 15:39 UTCEG score recompute
  3. 2026-10-11 19:24 UTCEG score recompute
  4. 2026-10-11 16:40 UTCEG score recompute
  5. 2026-10-11 13:59 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-11 02:41 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-10 01:21 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-08 21:59 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-08 09:26 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-06 19:38 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-05 18:18 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-05 05:46 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-03 16:05 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-03 03:33 UTCEG score recompute
  24. 2026-10-02 02:28 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  26. 2026-10-01 01:23 UTCEG score recompute
  27. 2026-09-30 00:18 UTCEG score recompute
  28. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  29. 2026-09-29 09:08 UTCEG score recompute
  30. 2026-09-28 20:29 UTCEG score recompute
  31. 2026-09-28 19:49 UTCEG score recompute
  32. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-09-27 22:34 UTCEG score recompute
  34. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-09-26 21:28 UTCEG score recompute
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-09-26 08:56 UTCEG score recompute
  38. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  39. 2026-09-24 18:32 UTCEG score recompute
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  41. 2026-09-24 06:00 UTCEG score recompute
  42. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-09-22 16:19 UTCEG score recompute
  44. 2026-09-22 15:45 UTCEG score recomputeFirst assessed: 7.7 HIGH
  45. 2026-09-22 15:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75608?
CVE-2026-75608 is a high-severity vulnerability; its CVE record was published on September 22, 2026. Frigate is an open source network video recorder. Prior to 0.18.0, the prefix-matched location /api/go2rtc/api in docker/main/rootfs/usr/local/nginx/conf/nginx.conf requires authentication but does not require an administrator role for GET requests, exposing the proxied go2rtc API to viewer users.…
When was the CVE record for CVE-2026-75608 published?
The CVE record for CVE-2026-75608 was published on September 22, 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 September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-75608 actively exploited?
CVE-2026-75608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75608?
CVE-2026-75608 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75608?
A fix for CVE-2026-75608 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-75608?

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