# CVE-2025-46750: Authentication Bypass

> Local attackers can bypass BIOS password authentication by importing a settings file, allowing unauthorized modification of protected BIOS configurations.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-9j22-g5g3-cw39

## What is CVE-2025-46750?

CVE-2025-46750 is a medium-severity authentication bypass vulnerability in Schweitzer Engineering Laboratories SEL-3350-1, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SEL BIOS packages prior to 1.3.49152.117 or 2.6.49152.98 allow a local attacker to bypass password authentication and change password-protected  BIOS settings by importing a BIOS settings file with no password set.

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

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


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

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

## Is CVE-2025-46750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46750 is a medium-severity authentication bypass vulnerability in Schweitzer Engineering Laboratories SEL-3350-1, published on 12 May 2025. 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-46750 in the wild and no public exploit code.

Affected product: Schweitzer Engineering Laboratories SEL-3350-1. 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-46750/ (Markdown: https://insights.sbomify.com/CVE-2025-46750/index.md)
```

## Sources

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

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