# CVE-2025-4994: Authentication Bypass for SafeLine SL6 and SL6+

> Attackers within Bluetooth range can bypass authentication to gain unauthorized administrative access to SafeLine SL6/SL+ elevator intercom devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-95pw-q9xh-p66r

## What is CVE-2025-4994?

CVE-2025-4994 is a high-severity authentication bypass vulnerability in SafeLine SL6/SL6+, published on 22 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SafeLine SL6 and SL6+ devices integrated into elevator emergency intercom systems are vulnerable to an authentication bypass. This vulnerability allows attackers to bypass authentication requirements and access the device's configuration service via the Bluetooth Low Energy (BLE) interface. Consequently, an attacker within wireless range can gain unauthorized administrative access to the device configuration.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2025-4994?


## How do I fix CVE-2025-4994?

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

## Is CVE-2025-4994 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4994 and fix it if it is affected.

What it is: CVE-2025-4994 is a high-severity authentication bypass vulnerability in SafeLine SL6/SL6+, published on 22 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4994 in the wild and no public exploit code.

Affected product: SafeLine SL6/SL6+. 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-2025-4994/ (Markdown: https://insights.sbomify.com/CVE-2025-4994/index.md)
```

## Sources

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

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