# CVE-2025-42895: Code Injection vulnerability in SAP HANA JDBC Client

> A high-privilege local user can inject code via crafted JDBC connection parameters, causing unauthorized code loading and potential denial of service.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-m452-g496-4chp

## What is CVE-2025-42895?

CVE-2025-42895 is a medium-severity code injection vulnerability in SAP_SE SAP HANA JDBC Client, published on 11 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Due to insufficient validation of connection property values, the SAP HANA JDBC Client allows a high-privilege locally authenticated user to supply crafted parameters that lead to unauthorized code loading, resulting in low impact on confidentiality and integrity and high impact on availability of the application.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-42895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42895 is a medium-severity code injection vulnerability in SAP_SE SAP HANA JDBC Client, published on 11 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-42895 in the wild and no public exploit code.

Affected product: SAP_SE SAP HANA JDBC Client. 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-42895/ (Markdown: https://insights.sbomify.com/CVE-2025-42895/index.md)
```

## Sources

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

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