# CVE-2026-100501: Flame through 2.4.0 Brute-Force Attack via Login Endpoint

> Unauthenticated attackers can brute-force admin passwords due to missing rate limiting, gaining full administrative access to modify application configuration.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-r7p3-q524-5mc7

## What is CVE-2026-100501?

CVE-2026-100501 is a high-severity authentication bypass vulnerability in pawelmalak flame, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flame through 2.4.0 contains an improper restriction of excessive authentication attempts vulnerability in the POST /api/auth login endpoint that allows unauthenticated attackers to brute-force the admin password. Attackers can submit unlimited password guesses without rate limiting, attempt counters, lockouts, or delays to gain full administrator access and modify application configuration.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-100501?


## How do I fix CVE-2026-100501?

No fix has been published for CVE-2026-100501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100501 being exploited?

There is no known exploitation of CVE-2026-100501 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100501 and fix it if it is affected.

What it is: CVE-2026-100501 is a high-severity authentication bypass vulnerability in pawelmalak flame, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100501 in the wild and no public exploit code.

Affected product: pawelmalak flame. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100501/ (Markdown: https://insights.sbomify.com/CVE-2026-100501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100501
- OSV: https://osv.dev/vulnerability/CVE-2026-100501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100501/
Summaries are generated and may contain mistakes; the official description above is the record.