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

New CVE Detected

CVE-2026-71805 – Unauthenticated Arbitrary File Upload / Path Traversal (RCE risk) – LZ-litchi ≤ 1.0

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

Summary

CVE-2026-71805 is a critical (CVSS 9.8) unauthenticated arbitrary file upload and path traversal vulnerability in LZ-litchi, a Java-based rapid development platform, affecting version 1.0.0 (and earlier). The flaw allows unauthenticated, remote attackers to upload files to arbitrary filesystem locations and subsequently retrieve them, forming a complete anonymous read/write attack chain that can lead to remote code execution or full system compromise.

Technical details

  • Root cause: The file upload endpoint is annotated with @PermitAll, bypassing authentication, and the user-supplied directory parameter is concatenated directly into the server’s base storage path (config.getBasePath() + File.separator + path) without canonicalization or filtering of ../ sequences.
  • Trigger conditions: An attacker sends a crafted multipart POST request to /app-api/infra/file/upload with a directory value containing directory traversal sequences (e.g., ../../../../../../tmp) and an arbitrary file payload; the file type restriction (fileType=all in default/demo configuration) does not block dangerous file extensions.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: Attackers can write files outside the intended upload directory (potentially including web-accessible or executable paths) and, via a related unauthenticated download endpoint (GET /admin-api/infra/file/{configKey}/get/**, also @PermitAll and only URL-decoding paths without filtering ../), read arbitrary files from the server. Combined, these primitives can be leveraged to plant and later retrieve/execute malicious files, resulting in high confidentiality, integrity, and availability impact.

Affected software

  • LZ-litchi Rapid Development Platform, version 1.0.0 and earlier (≤ 1.0.0)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CWE: CWE-434 (Unrestricted Upload of File with Dangerous Type)

Mitigation and recommended actions

  • Immediate: Upgrade LZ-litchi to a version beyond 1.0.0 that removes the @PermitAll annotation from the file upload (/app-api/infra/file/upload, /app-api/infra/file/create) and file download (/admin-api/infra/file/{configKey}/get/**) endpoints and requires proper authentication.
  • If no patch is available:
    • Restrict or disable public access to the affected upload and download endpoints at the network/reverse-proxy layer until a fix is applied.
    • Implement server-side path normalization/canonicalization (e.g., getCanonicalPath()) to reject requests where the resolved path escapes the configured base upload directory.
    • Enforce an allow-list of permitted file extensions/types instead of relying on an "allow all" configuration.
    • Generate randomized, server-controlled filenames and storage paths rather than trusting user-supplied directory or filename values.
    • Deploy WAF rules to detect and block path traversal sequences (../, encoded variants) in upload-related POST parameters as a temporary compensating control.

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