# CVE-2026-58375: JimuReport 2.5.0 - Unauthenticated Report Export via /jmreport/auto/export

> Unauthenticated attackers can export any report via the auto-export endpoint, exposing sensitive data and embedded credentials.

- **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:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-cg8w-ggx5-v8p7

## What is CVE-2026-58375?

CVE-2026-58375 is a high-severity missing authorization vulnerability in jeecgboot jimureport, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JimuReport through 2.5.0 exposes the POST /jmreport/auto/export endpoint without authentication: the handler is annotated @JimuNoLoginRequired, so JimuReportTokenInterceptor skips all authentication and authorization, and the export service streams the rendered report for any supplied report id without verifying the auto-export configuration flag. An unauthenticated remote attacker can enumerate Snowflake report identifiers and export the full contents of any report, including the data returned by the report configured SQL queries and any credentials embedded in its data sources.

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

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


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

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

## Is CVE-2026-58375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58375 is a high-severity missing authorization vulnerability in jeecgboot jimureport, published on 30 Jun 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-58375 exists.

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

## Sources

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

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