# CVE-2025-37103: Hardcoded Credential Exposure Allows Unauthorized Access in Web Interface

> Hardcoded credentials in HPE Instant On Access Points allow remote attackers to bypass authentication and gain administrative access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-5xp3-2ff8-9grr

## What is CVE-2025-37103?

CVE-2025-37103 is a critical vulnerability in Hewlett Packard Enterprise (HPE) HPE Networking Instant On, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hard-coded login credentials were found in HPE Networking Instant On  Access Points, allowing anyone with knowledge of it to bypass normal  device authentication. Successful exploitation could allow a remote  attacker to gain administrative access to the system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-37103 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-37103 is a critical vulnerability in Hewlett Packard Enterprise (HPE) HPE Networking Instant On, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37103 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE Networking Instant On. 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-37103/ (Markdown: https://insights.sbomify.com/CVE-2025-37103/index.md)
```

## Sources

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

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