dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-11458

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A weakness has been identified in erzhongxmu JeeWMS up to 141740afb2ba14d441c82a833d0a418d07ca2d69. This issue affects some unknown processing of the file /base-boot/actuator of the component Boot Actuator Endpoint. Executing a manipulation can lead to information disclosure. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in the Spring Boot Actuator endpoint at /base-boot/actuator in erzhongxmu JeeWMS. Exposed actuator endpoints can leak sensitive application information including environment variables, configuration details, heap dumps, thread traces, and internal system data. The attack requires no authentication and can be exploited remotely.

MitigationSecure or disable Spring Boot Actuator endpoints by implementing authentication/authorization via Spring Security, restricting network access, and disabling sensitive endpoints (like /env, /heapdump, /threaddump) or exposing only health checks to unauthenticated users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the target is erzhongxmu JeeWMS
    Probe the application for JeeWMS-specific paths or banners. Check the application homepage or API documentation for product identification.
    Affected if The application is confirmed to be erzhongxmu JeeWMS.
  2. Verify the actuator endpoint is accessible
    Send an HTTP GET request to http://target/base-boot/actuator without providing any authentication credentials. Check for a 200 OK response with JSON actuator data.
    Affected if The endpoint returns actuator JSON output without requiring login or authentication.
  3. Check for sensitive actuator endpoints
    Probe common sensitive actuator paths such as /base-boot/actuator/env, /base-boot/actuator/heapdump, /base-boot/actuator/trace, /base-boot/actuator/mappings, and /base-boot/actuator/beans without authentication.
    Affected if Any of these endpoints return sensitive configuration, environment variables, heap dumps, or internal application state without authentication.
  4. Inspect application configuration for actuator exposure
    Locate the application.properties or application.yml file (typically in the classpath or config directory) and check for management.endpoints.web.exposure.include and related settings.
    Affected if The configuration shows actuator endpoints are exposed via 'include' settings without being restricted by 'base-boot' or requiring authentication.

A user is affected if they are running erzhongxmu JeeWMS and the /base-boot/actuator endpoint (or specific sensitive actuator endpoints) is reachable without authentication, exposing system configuration or internal state.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Secure or disable Spring Boot Actuator endpoints by implementing authentication/authorization via Spring Security, restricting network access, and disabling sensitive endpoints (like /env, /heapdump, /threaddump) or exposing only health checks to unauthenticated users.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11458 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data