# CVE-2026-100502: Flame through 2.4.0 Admin Token Insufficient Session Expiration

> Attackers with former admin access can mint permanent administrator tokens by manipulating duration parameters, bypassing session expiration and retaining dashboard control.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-h3fx-87pr-c7fx

## What is CVE-2026-100502?

CVE-2026-100502 is a medium-severity authentication bypass vulnerability in pawelmalak flame, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Flame through 2.4.0 contains an insufficient session expiration vulnerability in the login endpoint that allows attackers with former admin access to obtain tokens with arbitrary lifespans by supplying unvalidated duration parameters. Attackers can mint near-permanent administrator tokens that survive password changes, retaining full control of the dashboard since tokens are verified only against a static JWT secret that is never rotated.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-100502 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100502 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100502 is a medium-severity authentication bypass vulnerability in pawelmalak flame, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100502 exists.

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-100502/ (Markdown: https://insights.sbomify.com/CVE-2026-100502/index.md)
```

## Sources

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

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