CVE-2026-54495

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

Score 4.3 from GitHub Security Advisory published 2026-07-15. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
4.3EG
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: 4.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The OpenFeature Operator allows users to expose feature flags to applications. In version 0.9.2 and earlier, a tenant who can create a controller-owned workload can use the openfeature.dev/featureflagsource annotation with NAMESPACE/NAME syntax to reference a FeatureFlagSource or InProcessConfiguration in another namespace. On multi-tenant clusters that use namespaces as trust boundaries, the cluster-scoped operator reads that resource and materializes spec.envVars literal values, spec.httpSyncBearerToken, sync URIs, and supporting ConfigMaps into the tenant's workload. Single-tenant clusters are not impacted, secretKeyRef and configMapKeyRef values remain namespace-local, and creating a FeatureFlagSource is not required.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
The EG Score, 4.3 of 10.
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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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

July 15, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
No fix on record yet. Sources: github.
Web page

Add ClusterFeatureFlagSource / ClusterInProcessConfiguration, remove implicit cross-namespace resolution · Issue #847 · open-feature/open-feature-operator · GitHub

https://github.com/open-feature/open-feature-operator/issues/847
GitHub advisoryMentions a patch (unverified)

Cross-namespace FeatureFlagSource and InProcessConfiguration resolution exposes spec contents on multi-tenant clusters · Advisory · open-feature/open-feature-operator · GitHub

https://github.com/open-feature/open-feature-operator/security/advisories/GHSA-398h-7f66-3h4p

Vendor Advisories for CVE-2026-54495(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/open-feature/open-feature-operator—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/open-feature/open-feature-operator—
  • every version through 0.9.2: no fix on record
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-12 15:56 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-01 12:35 UTCEG score recompute
  18. 2026-10-01 12:35 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-28 08:40 UTCEG score recompute
  23. 2026-09-28 08:40 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 63 more
  1. 2026-09-24 21:26 UTCEG score recompute
  2. 2026-09-24 21:26 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  3. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-09-24 08:45 UTCEG score recompute
  5. 2026-09-24 08:45 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  6. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-09-23 03:13 UTCEG score recompute
  8. 2026-09-23 03:13 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  9. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-09-18 15:27 UTCEG score recompute
  12. 2026-09-18 15:27 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  13. 2026-09-18 14:54 UTCEG score recompute
  14. 2026-09-18 14:54 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  15. 2026-09-17 20:18 UTCEG score recompute
  16. 2026-09-17 20:18 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  17. 2026-09-17 19:52 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  18. 2026-09-14 08:04 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  19. 2026-09-13 07:11 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  20. 2026-09-11 21:43 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  21. 2026-09-08 00:40 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  22. 2026-09-05 20:45 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  23. 2026-08-31 04:36 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  24. 2026-08-30 03:43 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  25. 2026-08-27 15:20 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  26. 2026-08-26 14:25 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  27. 2026-08-25 13:28 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  28. 2026-08-24 12:31 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  29. 2026-08-23 11:29 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  30. 2026-08-22 10:36 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  31. 2026-08-21 09:42 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  32. 2026-08-20 08:49 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  33. 2026-08-19 07:56 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  34. 2026-08-18 07:01 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  35. 2026-08-17 06:07 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  36. 2026-08-16 05:14 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  37. 2026-08-15 04:22 UTCEG score recompute
  38. 2026-08-15 04:22 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  39. 2026-08-14 03:26 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  40. 2026-08-13 02:33 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  41. 2026-08-12 01:41 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  42. 2026-08-11 00:48 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  43. 2026-08-09 23:55 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  44. 2026-08-08 23:03 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  45. 2026-08-07 22:10 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  46. 2026-08-06 21:17 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  47. 2026-08-05 20:24 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  48. 2026-08-04 19:32 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  49. 2026-08-03 18:39 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  50. 2026-08-02 17:47 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  51. 2026-08-01 16:54 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  52. 2026-07-31 16:01 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  53. 2026-07-30 15:07 UTCEG score recompute
  54. 2026-07-30 15:06 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  55. 2026-07-29 14:12 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  56. 2026-07-28 13:18 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  57. 2026-07-27 12:24 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  58. 2026-07-26 11:28 UTCEG score recompute
  59. 2026-07-26 11:28 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  60. 2026-07-23 03:19 UTCEG score recompute
  61. 2026-07-16 23:47 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3
  62. 2026-07-15 22:54 UTCEG score recompute
  63. 2026-07-15 22:54 UTCGHSA enrichmentGHSA-398h-7f66-3h4p · GitHub CVSS 4.3

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/open-feature/open-feature-operator

Frequently asked(5)

What is CVE-2026-54495?
CVE-2026-54495 is a medium-severity vulnerability; its CVE record was published on July 15, 2026. The OpenFeature Operator allows users to expose feature flags to applications. In version 0.9.2 and earlier, a tenant who can create a controller-owned workload can use the openfeature.dev/featureflagsource annotation with NAMESPACE/NAME syntax to reference a FeatureFlagSource or…
When was the CVE record for CVE-2026-54495 published?
The CVE record for CVE-2026-54495 was published on July 15, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-54495 actively exploited?
CVE-2026-54495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54495?
CVE-2026-54495 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54495?
No fix for CVE-2026-54495 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-54495 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-54495

Explore →

Is Your Infrastructure Affected by CVE-2026-54495?

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

Book a Demo →Browse All CVEs