CVE-2026-44300

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (55th 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-78874 (ENISA EUVD) · GHSA-wmj8-9953-vff5 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenCost provides cost monitoring for Kubernetes workloads and cloud costs. Prior to 1.121.0, the POST /serviceKey endpoint in pkg/costmodel/router.go allows a network client to invoke AddServiceKey without mandatory authentication and submit an arbitrary key form value that is written to the GCP service-account key.json file returned by GetGCPAuthSecretFilePath in core/pkg/env/core.go. The attacker controls the file contents but not the CONFIG_PATH-derived directory, the key.json filename, or the file mode. Replacing the credential contents can disrupt GCP cost collection or cause OpenCost to use attacker-selected credentials, and the wildcard Access-Control-Allow-Origin response permits browser-assisted requests when the service is reachable from a browser. This issue is fixed in version 1.121.0.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.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 total (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
0.8%
EPSS %ILE
55th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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: 3 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 total (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)3 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 total (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 14, 2026

Last Modified

September 30, 2026

Advisory Details (7)

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

v1.121.0

Patch available: opencost/opencost v1.121.0

https://github.com/opencost/opencost/releases/tag/v1.121.0
GitHub release Patch Available

v1.120.0

Patch available: opencost/opencost v1.120.0

https://github.com/opencost/opencost/releases/tag/v1.120.0
GitHub commit Patch Available

commit a49a25bc2e0d (opencost/opencost)

Patch available: opencost/opencost v1.121.0 (contains commit a49a25bc2e0d)

https://github.com/opencost/opencost/commit/a49a25bc2e0d6e220a131a4dc58f38ebe6ae851b
GitHub commit Patch Available

commit 69430e7f627b (opencost/opencost)

Patch available: opencost/opencost v1.120.0 (contains commit 69430e7f627b)

https://github.com/opencost/opencost/commit/69430e7f627b3e62c8999312c06949267fab813a
GitHub pull request Patch Available

deactivate endpoints unless admin token set

Patch available: opencost/opencost v1.121.0 (PR #3910 merged 2026-07-09)

https://github.com/opencost/opencost/pull/3910
GitHub pull request Patch Available

add middleware for auth

Patch available: opencost/opencost v1.120.0 (PR #3651 merged 2026-03-12)

https://github.com/opencost/opencost/pull/3651
GitHub advisoryMentions a patch (unverified)

OpenCost ServiceKey Endpoint Unauthorized Credential Overwrite/Injection · Advisory · opencost/opencost · GitHub

https://github.com/opencost/opencost/security/advisories/GHSA-wmj8-9953-vff5

Vendor Advisories for CVE-2026-44300(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/opencost/opencost @ 1.119.1 (fixes < 1.119.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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/opencost/opencost—
  • every version up to 1.119.1: fixed in 1.119.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-11-01 07:49 UTCGHSA enrichmentGHSA-wmj8-9953-vff5 · GitHub severity HIGH
  3. 2026-11-01 07:49 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-30 18:55 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-25 14:27 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-24 04:28 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-10-18 03:39 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-10-17 14:00 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 39 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  4. 2026-10-12 16:05 UTCEG score recompute
  5. 2026-10-11 19:47 UTCEG score recompute
  6. 2026-10-11 17:02 UTCEG score recompute
  7. 2026-10-11 14:27 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-09-30 17:53 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-09-28 09:10 UTCEG score recompute
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-09-24 09:09 UTCEG score recompute
  24. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-09-23 03:42 UTCEG score recompute
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-09-18 04:53 UTCEG score recompute
  29. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-09-15 20:47 UTCEG score recompute
  32. 2026-09-15 19:50 UTCEG score recompute
  33. 2026-09-15 18:36 UTCEG score recompute
  34. 2026-09-15 17:23 UTCEG score recomputeFirst assessed: 8.8 HIGH
  35. 2026-09-15 17:22 UTCMITRE cvelistV5CVSS v3 → 8.8 · CVSS v4 → 8.8
  36. 2026-08-01 12:48 UTCEG score recompute
  37. 2026-07-26 11:44 UTCEG score recompute
  38. 2026-07-23 03:15 UTCEG score recompute
  39. 2026-07-14 17:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44300?
CVE-2026-44300 is a high-severity vulnerability; its CVE record was published on July 14, 2026. OpenCost provides cost monitoring for Kubernetes workloads and cloud costs. Prior to 1.121.0, the POST /serviceKey endpoint in pkg/costmodel/router.go allows a network client to invoke AddServiceKey without mandatory authentication and submit an arbitrary key form value that is written to the GCP…
When was the CVE record for CVE-2026-44300 published?
The CVE record for CVE-2026-44300 was published on July 14, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-44300 actively exploited?
CVE-2026-44300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44300?
CVE-2026-44300 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44300?
A fix for CVE-2026-44300 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44300 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-2026-44300

Explore →

Is Your Infrastructure Affected by CVE-2026-44300?

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