# CVE-2025-46690: Missing authorization in Ververica Platform

> Low-privileged users can access SQL connectors via direct API requests, potentially exposing sensitive configuration data.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-h4xx-369g-v8j6

## What is CVE-2025-46690?

CVE-2025-46690 is a medium-severity missing authorization vulnerability in Ververica Platform, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ververica Platform 2.14.0 allows low-privileged users to access SQL connectors via a direct namespaces/default/formats request.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Ververica Ververica Platform.

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

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

## Is CVE-2025-46690 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46690 exists.

## Other vulnerabilities in Ververica Platform

- [CVE-2025-46689](https://insights.sbomify.com/CVE-2025-46689/): Cross-site scripting in Ververica Platform (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46690 is a medium-severity missing authorization vulnerability in Ververica Platform, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46690 exists.

Affected product: Ververica Platform. 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-46690/ (Markdown: https://insights.sbomify.com/CVE-2025-46690/index.md)
```

## Sources

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

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