# CVE-2026-92749: SafeLine through 9.4.1 Authentication Bypass via Weak Session Secret

> Attackers can forge administrator session cookies by predicting weak session secrets, gaining unauthorized control of the SafeLine management console.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-9q3x-j473-5399

## What is CVE-2026-92749?

CVE-2026-92749 is a critical vulnerability in chaitin SafeLine, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SafeLine through 9.4.1 derives the management console session-signing secret from a time-seeded math/rand generator, allowing attackers to reconstruct the key offline. Unauthenticated remote attackers who can bound the install timestamp can regenerate the secret and forge valid administrator session cookies to gain control of protected sites.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-92749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92749 is a critical vulnerability in chaitin SafeLine, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92749 exists.

Affected product: chaitin SafeLine. 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-92749/ (Markdown: https://insights.sbomify.com/CVE-2026-92749/index.md)
```

## Sources

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

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