Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-91996 – Unauthenticated JVM Property Disclosure – dromara lamp-cloud ≤ 5.10.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-91996 is a missing authentication vulnerability (CWE-306) in dromara’s lamp-cloud framework, affecting all versions through 5.10.0. The application whitelists the path pattern /*/anno/** for anonymous access, which unintentionally exposes the code-generator endpoint /defGenProject/anno/getProperties to unauthenticated requests, letting any remote attacker dump the server’s full JVM system property map. This is a high-severity, network-exploitable information disclosure issue with no authentication or user interaction required.

Technical details

  • Root cause: lamp-cloud’s security configuration (IgnoreProperties.java) whitelists the wildcard path pattern /*/anno/** as permitted for anonymous, unauthenticated access.
  • Trigger conditions: The whitelist pattern also matches the code-generator controller endpoint /defGenProject/anno/getProperties (DefGenProjectController), which was not intended to be publicly reachable.
  • Attack vector: A remote, unauthenticated attacker sends a POST request directly to /defGenProject/anno/getProperties; the network attack vector requires low complexity, no privileges, and no user interaction.
  • Impact: The endpoint returns the full JVM system property map, disclosing sensitive information such as the JVM classpath, filesystem paths, operating system details, and startup secrets — information that can materially assist further attacks against the host.

Affected software

  • dromara/lamp-cloud, all versions from 0 through 5.10.0 (inclusive)

Severity

  • CVSS v4.0 Base Score: 8.7 (High) — 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
  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade lamp-cloud to a version newer than 5.10.0 that removes the code-generator endpoint from the /*/anno/** anonymous-access whitelist, or confirm with the vendor that a fix has been released and apply it.
  • If no patch is available: Remove or narrow the /*/anno/** whitelist entry so it no longer matches /defGenProject/anno/getProperties; restrict or disable the code-generator module in production deployments; block external access to code-generator endpoints at the network/reverse-proxy layer; and monitor for POST requests to /defGenProject/anno/getProperties from untrusted sources.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge