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-100501 Overview
CVE-2026-100501 is an improper restriction of excessive authentication attempts vulnerability [CWE-307] in Flame through version 2.4.0. The flaw resides in the POST /api/auth login endpoint, which accepts unlimited password submissions without rate limiting, attempt counters, account lockouts, or response delays. Unauthenticated attackers reachable over the network can brute-force the single administrator password and gain full control over the application configuration. Flame is a self-hosted startpage frequently deployed in homelab and small-business environments, often exposed to the internet via reverse proxies, which widens the practical attack surface.
Critical Impact
Unauthenticated network attackers can brute-force the Flame administrator password and modify application configuration without detection.
Affected Products
- Flame startpage, all versions through 2.4.0
- The vulnerable controllers/auth/login.js login handler
- Docker deployments based on the v2.4.0 reference Dockerfile
Discovery Timeline
- 2026-09-25 - CVE-2026-100501 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-100501
Vulnerability Analysis
Flame uses a single administrator password to gate configuration changes. The authentication route defined in routes/auth.js forwards requests directly to the login controller in controllers/auth/login.js. That handler compares the submitted password against the stored hash and returns a token on success, but it never records failed attempts, enforces per-IP throttling, or introduces an artificial delay. Because the endpoint is unauthenticated and the password space is bounded by whatever the operator chose, an attacker can automate guesses at the full speed the server will accept. Successful compromise yields administrator access, allowing the attacker to modify bookmarks, applications, themes, and other configuration entries, and to pivot users to attacker-controlled destinations.
Root Cause
The root cause is the absence of any brute-force mitigation in the login path. There is no middleware for rate limiting, no counter persisted alongside the credential store, and no exponential backoff on repeated failures. The design assumes a strong operator-chosen password is sufficient, which fails against automated password spraying and dictionary attacks.
Attack Vector
Exploitation requires only network reachability to the Flame web interface and the ability to send HTTP POST requests to /api/auth. An attacker iterates through a wordlist, submitting each candidate password in the JSON body of the request and inspecting the response for a successful token issuance. See the VulnCheck advisory on Flame and the vulnerable login controller source for the full technical description. No verified public proof-of-concept code is referenced in the advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-100501
Indicators of Compromise
- High volumes of POST /api/auth requests from a single source address or small set of addresses within a short time window.
- Repeated HTTP 401 or equivalent authentication-failure responses from the Flame instance, followed by a successful 200 response and token issuance.
- Unexpected changes to Flame bookmarks, applications, categories, or theme settings not performed by the legitimate administrator.
Detection Strategies
- Ingest reverse-proxy or application access logs into a SIEM and alert on bursts of requests to the /api/auth path.
- Correlate authentication-failure response codes against source IP to identify sustained guessing patterns.
- Baseline normal administrator login frequency and alert on deviations, including off-hours successful logins.
Monitoring Recommendations
- Enable verbose access logging on the reverse proxy fronting Flame and retain logs long enough to investigate slow brute-force campaigns.
- Monitor outbound links from the Flame configuration for unexpected modifications that could redirect users to malicious destinations.
- Track container and host-level network connections to the Flame port for anomalous external sources.
How to Mitigate CVE-2026-100501
Immediate Actions Required
- Restrict network exposure of the Flame interface to trusted networks or require VPN access until a fix is available.
- Place Flame behind a reverse proxy that enforces rate limiting and IP-based lockouts on the /api/auth endpoint.
- Rotate the Flame administrator password to a long, high-entropy value that resists dictionary attacks.
Patch Information
At the time of NVD publication on 2026-09-25, Flame versions through 2.4.0 are affected and no fixed release is referenced in the advisory. Operators should monitor the Flame GitHub repository and GitHub Issue #494 for an upstream fix and apply it when published.
Workarounds
- Front Flame with a reverse proxy such as nginx, Caddy, or Traefik and configure request rate limiting on /api/auth (for example, a low requests-per-minute threshold per source IP with temporary bans on excess).
- Add an additional authentication layer in front of Flame, such as HTTP Basic authentication at the proxy, OAuth2 proxy, or an identity-aware access gateway.
- Restrict access using firewall rules, Cloudflare Access, Tailscale, or WireGuard so only authenticated users can reach the login endpoint.
- Enable fail2ban or an equivalent log-driven blocker to automatically ban source addresses that generate repeated authentication failures.
# Example nginx rate limit for the Flame /api/auth endpoint
limit_req_zone $binary_remote_addr zone=flame_auth:10m rate=5r/m;
server {
listen 443 ssl;
server_name flame.example.com;
location /api/auth {
limit_req zone=flame_auth burst=5 nodelay;
limit_req_status 429;
proxy_pass http://flame_backend;
}
location / {
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

