CVE-2026-100418

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-26. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

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

Flame through 2.4.0 contains an information exposure vulnerability in the unauthenticated GET /api/config endpoint that returns the entire configuration object without field redaction. Attackers can retrieve the stored weather API key and internal operational settings by sending a single unauthenticated request to consume provider quota or access sensitive configuration data.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/100CISA SSVC

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. 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, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. 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, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 30, 2026

Advisory Details (6)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

Flame through 2.4.0 Information Exposure via GET /api/config | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flame-through-2.4.0-information-exposure-via-get-api-config
generic

GitHub - pawelmalak/flame: Flame is self-hosted startpage for your server. Easily manage your apps and bookmarks with built-in editors. · GitHub

https://github.com/pawelmalak/flame
generic

flame/utils/init/initialConfig.json at 3e03c25138df4321143c4fbd1a99468ff375ebb2 · pawelmalak/flame · GitHub

https://github.com/pawelmalak/flame/blob/3e03c25138df4321143c4fbd1a99468ff375ebb2/utils/init/initialConfig.json#L2
generic

flame/routes/config.js at 3e03c25138df4321143c4fbd1a99468ff375ebb2 · pawelmalak/flame · GitHub

https://github.com/pawelmalak/flame/blob/3e03c25138df4321143c4fbd1a99468ff375ebb2/routes/config.js#L14
generic

flame/controllers/config/getConfig.js at 3e03c25138df4321143c4fbd1a99468ff375ebb2 · pawelmalak/flame · GitHub

https://github.com/pawelmalak/flame/blob/3e03c25138df4321143c4fbd1a99468ff375ebb2/controllers/config/getConfig.js#L7-L13
generic

Security Report: Multiple vulnerabilities in Flame · Issue #494 · pawelmalak/flame · GitHub

https://github.com/pawelmalak/flame/issues/494

Vendor Advisories for CVE-2026-100418(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 26× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 05:23 UTCEG score recompute
  2. 2026-10-05 05:23 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 07:40 UTCEG score recompute
  5. 2026-10-04 07:40 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-03 09:58 UTCEG score recompute
  8. 2026-10-03 09:58 UTCGHSA enrichment
  9. 2026-10-02 12:12 UTCEG score recompute
  10. 2026-10-02 12:12 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 14:27 UTCGHSA enrichment
  13. 2026-09-30 16:45 UTCGHSA enrichment
  14. 2026-09-30 16:17 UTCEG score recompute
  15. 2026-09-30 16:17 UTCGHSA enrichment
  16. 2026-09-30 15:02 UTCEPSS rescore
  17. 2026-09-29 18:17 UTCEG score recompute
  18. 2026-09-29 18:17 UTCGHSA enrichment
  19. 2026-09-29 17:58 UTCEG score recompute
  20. 2026-09-29 17:57 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 13:21 UTCEG score recompute
  23. 2026-09-29 13:21 UTCGHSA enrichment
  24. 2026-09-28 15:35 UTCEG score recompute
  25. 2026-09-28 15:35 UTCGHSA enrichment
Show 9 more
  1. 2026-09-28 13:50 UTCEPSS rescore
  2. 2026-09-27 17:48 UTCEG score recompute
  3. 2026-09-27 17:48 UTCGHSA enrichment
  4. 2026-09-26 20:06 UTCEG score recompute
  5. 2026-09-26 20:06 UTCGHSA enrichment
  6. 2026-09-26 15:58 UTCEPSS rescore
  7. 2026-09-25 22:22 UTCEG score recompute
  8. 2026-09-25 22:09 UTCEG score recompute
  9. 2026-09-25 22:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100418?
CVE-2026-100418 is a medium vulnerability published on September 25, 2026. Flame through 2.4.0 contains an information exposure vulnerability in the unauthenticated GET /api/config endpoint that returns the entire configuration object without field redaction. Attackers can retrieve the stored weather API key and internal operational settings by sending a single…
When was CVE-2026-100418 disclosed?
CVE-2026-100418 was first published on September 25, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100418 actively exploited?
CVE-2026-100418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100418?
CVE-2026-100418 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100418?
No fix for CVE-2026-100418 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-100418 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100418?

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

Book a Demo →Browse All CVEs