CVE-2026-58375

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
36.6%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

JimuReport 2.5.0 - Unauthenticated Report Export via /jmreport/auto/export | Advisories | VulnCheck

https://www.vulncheck.com/advisories/jimureport-unauthenticated-report-export-via-jmreport-auto-export
generic🟡 PoC Available

Unauthenticated report export via /jmreport/auto/export -- JimuReport 2.3.4 · Issue #4694 · jeecgboot/jimureport · GitHub

https://github.com/jeecgboot/jimureport/issues/4694

Vendor Advisories for CVE-2026-58375(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 40× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 03:44 UTCEG score recompute
  2. 2026-07-07 03:44 UTCGHSA enrichment
  3. 2026-07-06 16:36 UTCEG score recompute
  4. 2026-07-06 16:36 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 05:41 UTCEG score recompute
  8. 2026-07-06 05:41 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 18:44 UTCEG score recompute
  12. 2026-07-05 18:44 UTCGHSA enrichment
  13. 2026-07-05 07:49 UTCEG score recompute
  14. 2026-07-05 07:49 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 20:53 UTCEG score recompute
  18. 2026-07-04 20:53 UTCGHSA enrichment
  19. 2026-07-04 09:58 UTCEG score recompute
  20. 2026-07-04 09:58 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 23:03 UTCEG score recompute
  24. 2026-07-03 23:03 UTCGHSA enrichment
  25. 2026-07-03 12:04 UTCEG score recompute
Show 15 more
  1. 2026-07-03 12:04 UTCGHSA enrichment
  2. 2026-07-03 01:08 UTCEG score recompute
  3. 2026-07-03 01:08 UTCGHSA enrichment
  4. 2026-07-02 14:13 UTCEG score recompute
  5. 2026-07-02 14:13 UTCGHSA enrichment
  6. 2026-07-02 03:18 UTCEG score recompute
  7. 2026-07-02 03:18 UTCGHSA enrichment
  8. 2026-07-01 16:23 UTCEG score recompute
  9. 2026-07-01 16:23 UTCGHSA enrichment
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 05:28 UTCEG score recompute
  12. 2026-07-01 05:28 UTCGHSA enrichment
  13. 2026-06-30 18:33 UTCEG score recompute
  14. 2026-06-30 18:33 UTCGHSA enrichment
  15. 2026-06-30 18:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58375?
CVE-2026-58375 is a high vulnerability published on June 30, 2026. 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…
When was CVE-2026-58375 disclosed?
CVE-2026-58375 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58375 actively exploited?
CVE-2026-58375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58375?
CVE-2026-58375 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58375, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58375

Explore →

Is Your Infrastructure Affected by CVE-2026-58375?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs