Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-92749 – Authentication Bypass via Weak Session Secret – SafeLine WAF (through 9.4.1)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92749 is an authentication bypass vulnerability in the management console of SafeLine, a self-hosted web application firewall developed by Chaitin. The console’s session-signing secret is generated using a cryptographically weak, time-seeded pseudo-random number generator, allowing an attacker to reconstruct the secret offline and forge valid administrator session cookies. The flaw affects SafeLine versions through 9.4.1 and has been assigned a CVSS v4.0 base score of 9.2 (Critical).

Technical details

  • Root cause: The SafeLine web server’s RandStr utility function seeds Go’s math/rand generator with a time-based value (time.Now().UnixNano()) rather than a cryptographically secure source of randomness.
  • Trigger conditions: The management console’s session-signing key is generated via utils.RandStr(32), meaning its value is fully determined by the seed used at generation time (e.g., install/first-run time).
  • Attack vector: An unauthenticated remote attacker who can estimate or narrow down the installation/generation timestamp can brute-force or recompute the PRNG output space offline to reconstruct the session-signing secret.
  • Impact: Once the secret is recovered, the attacker can forge valid administrator session cookies for the SafeLine management console, gaining unauthorized administrative control over the WAF and the sites it protects — impacting confidentiality, integrity, and availability.
  • CWE classification: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator).

Affected software

  • Chaitin SafeLine — versions 0 through 9.4.1 (management console component).

Severity

  • CVSS v4.0: 9.2 (Critical) — 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
  • CVSS v3.1: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: At the time of publication, no vendor-confirmed patched release beyond 9.4.1 has been publicly documented. Organizations should monitor the official Chaitin SafeLine GitHub repository and release notes for a fix addressing the weak session-secret generation and upgrade as soon as a patched version is available.
  • If no patch is available:
    • Restrict network access to the SafeLine management console to trusted internal networks or VPNs, and do not expose it directly to the internet.
    • Rotate/regenerate the session-signing secret manually where the product allows, and restart the management service to force re-issuance of session tokens.
    • Enforce short session lifetimes and monitor for anomalous administrator logins or session activity.
    • Apply network-level access controls (allow-listing, IP restrictions) and enable multi-factor protections where supported to reduce the impact of a forged session.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge