# CVE-2026-111613: AllData through 0.7.1 Unauthenticated JDBC Injection via /jobJdbcDatasource/test

> Unauthenticated attackers can exploit JDBC injection to read arbitrary files from the server via malicious database connection parameters.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-33v5-488r-m83x

## What is CVE-2026-111613?

CVE-2026-111613 is a high-severity server-side request forgery vulnerability in alldatacenter alldata, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AllData through 0.7.1 contains an unauthenticated JDBC injection vulnerability that allows remote attackers to open arbitrary database connections by supplying jdbcUrl and jdbcDriverClass values to the data-dts /jobJdbcDatasource/test endpoint. Attackers can supply a MySQL JDBC URL with allowLoadLocalInfile=true pointing to an attacker-controlled server to read arbitrary files from the data-dts host.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111613 is a high-severity server-side request forgery vulnerability in alldatacenter alldata, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111613 exists.

Affected product: alldatacenter alldata. 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-111613/ (Markdown: https://insights.sbomify.com/CVE-2026-111613/index.md)
```

## Sources

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

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