# CVE-2026-120953: A URI redirection weakness exists in the authentication component of the Atlas SQL JDBC Driver.


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026

## What is CVE-2026-120953?

CVE-2026-120953 is a medium-severity vulnerability in MongoDB Atlas SQL JDBC Driver, published on 3 Nov 2026. 

### Official description

A URI redirection weakness exists in the authentication component of the Atlas SQL JDBC Driver. During an interactive sign-in flow the driver accepts endpoint addresses supplied by the remote endpoint it is pointed at without validating their scheme, and passes the resulting address to the local default protocol handler. An unauthenticated remote party that controls the endpoint a user elects to connect to may cause an address of its choosing to be opened on the user's system; user interaction is required.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-120953?


## How do I fix CVE-2026-120953?

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

## Is CVE-2026-120953 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120953 and fix it if it is affected.

What it is: CVE-2026-120953 is a medium-severity vulnerability in MongoDB Atlas SQL JDBC Driver, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120953 in the wild and no public exploit code.

Affected product: MongoDB Atlas SQL JDBC Driver. 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-2026-120953/ (Markdown: https://insights.sbomify.com/CVE-2026-120953/index.md)
```

## Sources

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

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