Quick answers
- Is CVE-2026-58377 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58377 being exploited in the wild.
- How severe is CVE-2026-58377?
- High severity, with a CVSS score of 8.1, published 30 June 2026.
- Which products and versions are affected?
- JeecgBoot through 3.9.2.
- Is there a fix for CVE-2026-58377?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58377 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58377?
- Check whether you run JeecgBoot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
JeecgBoot through 3.9.2 suffers from missing authorization checks in the OpenApiAuthController and OpenApiPermissionController components. These endpoints lack Shiro authorization annotations, allowing any authenticated user to perform create, read, update, and delete (CRUD) operations on OpenAPI Access Key/Secret Key (AK/SK) pairs. Furthermore, the /openapi/call/{path} handler fails to verify the SK-signed signature, relying solely on the AK provided in the request header. By combining these flaws, a low-privileged attacker can retrieve plaintext credentials for administrative accounts and invoke proxy API routes with the permissions of the credential owner, leading to full administrative impersonation.
Affected products
- JeecgBoot JeecgBoot through 3.9.2
Timeline
- 2026-06-14: disclosed: Issue reported on GitHub repository
- 2026-06-30: advisory: NVD and VulnCheck published advisory