Skip to main content
Vulnerability Database/CVE-2026-100418

CVE-2026-100418: Flame Information Disclosure Vulnerability

CVE-2026-100418 is an information disclosure flaw in Flame that exposes API keys and configuration data through an unauthenticated endpoint. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100418 Overview

CVE-2026-100418 is an information exposure vulnerability [CWE-200] in Flame versions through 2.4.0. The flaw resides in the unauthenticated GET /api/config endpoint, which returns the complete configuration object without field-level redaction. Any unauthenticated network attacker can retrieve the stored weather API key and internal operational settings with a single HTTP request. The exposure enables provider quota consumption, abuse of the leaked API key against third-party services, and reconnaissance of internal configuration data. Flame is a self-hosted startpage application for personal servers, commonly deployed in homelab and small-business environments.

Critical Impact

Unauthenticated remote attackers can retrieve stored weather API keys and application configuration data by issuing a single HTTP request to /api/config.

Affected Products

  • Flame versions through 2.4.0
  • Self-hosted Flame startpage deployments exposed to untrusted networks
  • Containerized Flame instances using default routing

Discovery Timeline

  • 2026-09-25 - CVE-2026-100418 published to NVD
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-100418

Vulnerability Analysis

Flame exposes a REST route at GET /api/config that serves the application's configuration. The route handler returns the entire configuration object as JSON without filtering sensitive fields. The endpoint lacks authentication middleware, allowing any network client that can reach the Flame instance to query it. The response includes the configured weather API key alongside operational settings, giving attackers direct access to a credential intended to remain server-side.

The impact is bounded to confidentiality of configuration data. Attackers can abuse the harvested API key to consume the victim's weather provider quota, incur billing, or correlate the key with other services. Internal settings leaked through the same response support further targeting of the host.

Root Cause

The root cause is missing output filtering in the configuration controller combined with missing authentication on the route. The handler at controllers/config/getConfig.js returns the raw configuration record. The route definition in routes/config.js registers the endpoint without an authentication guard. Sensitive fields such as the weather API key, seeded from utils/init/initialConfig.json, are therefore returned to any caller.

Attack Vector

Exploitation requires only network reachability to the Flame HTTP service. An attacker issues an unauthenticated GET request to /api/config and parses the JSON response for the weatherData.apiKey field and other configuration values. No user interaction, privileges, or chained vulnerabilities are required. See the VulnCheck Advisory on Flame and GitHub Issue #494 for additional technical context.

Detection Methods for CVE-2026-100418

Indicators of Compromise

  • Unauthenticated HTTP GET requests to /api/config originating from external or unexpected source IPs.
  • Unusual spikes in weather provider API usage or billing attributable to the configured API key.
  • Access patterns to the Flame instance from scanners or non-browser user agents.

Detection Strategies

  • Review web server and reverse proxy access logs for GET /api/config requests not initiated by the Flame web UI session flow.
  • Deploy network monitoring rules to alert on cleartext responses containing JSON fields such as weatherData or apiKey served from Flame hosts.
  • Correlate inbound requests to /api/config with outbound weather provider traffic to identify key abuse.

Monitoring Recommendations

  • Enable access logging on any reverse proxy fronting Flame and retain logs for at least 90 days.
  • Monitor weather provider dashboards for anomalous request volumes or requests from unexpected source IPs.
  • Alert on any public internet exposure of Flame management endpoints identified through external attack surface scans.

How to Mitigate CVE-2026-100418

Immediate Actions Required

  • Rotate the weather provider API key configured in Flame and invalidate the previously stored value.
  • Restrict network access to the Flame instance using firewall rules, VPN, or an authenticating reverse proxy.
  • Audit weather provider usage records for anomalous activity that may indicate the key was already harvested.

Patch Information

At the time of publication, no fixed Flame release is referenced in the enriched CVE data. Monitor the GitHub Repository for Flame and GitHub Issue #494 for an upstream fix. Apply any released patch that adds authentication to the configuration route and redacts sensitive fields from the response.

Workarounds

  • Place Flame behind a reverse proxy that enforces authentication such as HTTP basic auth, OAuth2 proxy, or mTLS, and block direct access to /api/config.
  • Deny external requests to /api/config at the proxy layer while permitting internal UI traffic.
  • Remove the weather API key from Flame configuration if the weather widget is not required, eliminating the sensitive value from the response.
bash
# Example nginx configuration to block external access to /api/config
location = /api/config {
    allow 192.168.0.0/16;
    allow 10.0.0.0/8;
    deny all;
    proxy_pass http://flame_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.