# CVE-2026-100418: Flame information exposure in unauthenticated config endpoint

Source: https://junglewise.ai/threats/cve-2026-100418-flame-through-2-4-0-contains-an-information-exposure  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-100418 · Severity: medium · CVSS 5.3 · Published 2026-09-25

Flame is a self-hosted startpage application that manages apps and bookmarks. An unauthenticated attacker can access the GET /api/config endpoint to retrieve the entire configuration object, including stored weather API keys and internal operational settings. This enables quota consumption abuse and exposure of sensitive configuration data that should not be publicly accessible.

Technologies: [Pawelmalak Flame](https://junglewise.ai/threats/technologies/flame). Vendors: [Pawelmalak](https://junglewise.ai/threats/vendors/pawelmalak).

## Quick answers

**Is CVE-2026-100418 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-100418 being exploited in the wild.

**How severe is CVE-2026-100418?** Medium severity, with a CVSS score of 5.3, published 25 September 2026.

**Which products and versions are affected?** Pawelmalak Flame through 2.4.0.

**Is there a fix for CVE-2026-100418?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-100418 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-100418?** Check whether you run Pawelmalak Flame at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The GET /api/config endpoint is marked with "Public" access and returns the full configuration object without field redaction. An unauthenticated network attacker can retrieve sensitive data including API keys and operational settings. The vulnerable code in getConfig.js loads and exposes the entire config object without filtering sensitive fields.

## Affected products

- pawelmalak Flame through 2.4.0

## Timeline

- 2026-09-25: disclosed

## References

- [https://github.com/pawelmalak/flame](https://github.com/pawelmalak/flame)
- [https://github.com/pawelmalak/flame/blob/3e03c25138df4321143c4fbd1a99468ff375ebb2/controllers/config/getConfig.js](https://github.com/pawelmalak/flame/blob/3e03c25138df4321143c4fbd1a99468ff375ebb2/controllers/config/getConfig.js)

## Related threats

- [Flame insufficient session expiration in login endpoint](https://junglewise.ai/threats/cve-2026-100502-flame-through-2-4-0-contains-an-insufficient-session-expiration)
- [Flame brute-force attack on authentication endpoint through 2.4.0](https://junglewise.ai/threats/cve-2026-100501-flame-through-2-4-0-contains-an-improper-restriction-of)