dbcve.org
InlongApplication · Apache

CVE-2025-27531

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data vulnerability in Apache InLong.  This issue affects Apache InLong: from 1.13.0 before 2.1.0, this issue would allow an authenticated attacker to read arbitrary files by double writing the param. Users are recommended to upgrade to version 2.1.0, which fixes the issue.

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

Apache InLong contains a deserialization vulnerability where an authenticated attacker can read arbitrary files by exploiting a double-write parameter technique. This critical (CVSS 9.8) issue affects versions 1.13.0 through 2.0.x and allows remote code execution or file disclosure through untrusted deserialized data.

MitigationUpgrade Apache InLong to version 2.1.0 or later to remediate this vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InlongApplication
Affected:>= 1.13.0, < 2.1.0

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
High
Integrity
High
Availability
High

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

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 Apache InLong is installed
    Check for InLong installation directories or running services. Common paths include /opt/inlong, /usr/local/inlong, or check running Java processes: ps aux | grep inlong
    Affected if Apache InLong is present in the environment
  2. Determine the installed InLong version
    Check the version file or jar manifest. Common locations: VERSION file in installation directory, or examine the version string in pom.xml if source is available. Also check: cat /path/to/inlong-version.txt or check docker image tags if using containers
    Affected if Installed version is >= 1.13.0 and < 2.1.0
  3. Check if the deserialization API endpoints are exposed
    Examine InLong configuration files (usually in conf/ or config/ directory) for API endpoint settings. Look for manager.api.host or similar configurations that expose the InLong Manager service to network
    Affected if Manager API is accessible from network without proper network segmentation
  4. Verify authentication configuration
    Review authentication settings in conf/application.yml or conf/inlong.conf. Check if authentication is enabled for API endpoints and whether default credentials are in use
    Affected if Authentication is disabled or using default credentials, allowing unauthenticated or easily guessed attacker access
  5. Identify if vulnerable deserialization features are enabled
    Check if InLong's data ingestion or serialization features are configured. Look for settings related to deserialization of untrusted data in source configurations, particularly any use of unsafe deserializers or lack of whitelist filtering
    Affected if Deserialization of untrusted data is permitted without strict type filtering or safelisting

Environment is affected if Apache InLong version 1.13.0 through 2.0.x is installed and its API/manager service is network-accessible to potential authenticated attackers.

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.

dbcve · scoped
Upgrade available Upgrade to 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Upgrade Apache InLong to version 2.1.0 or later to remediate this vulnerability.

Recommended fix High confidence

2.1.0

  1. 1. Plan and schedule a maintenance window for upgrading Apache InLong
  2. 2. Back up all InLong configurations, databases, and data directories
  3. 3. Stop all running InLong services gracefully
  4. 4. Upgrade InLong from the current version (1.13.0 to <2.1.0) to version 2.1.0
  5. 5. Review and migrate any configuration files that may have changed between versions
  6. 6. Start InLong services and verify they are running correctly
  7. 7. Validate that the deserialization vulnerability is resolved by testing that arbitrary file read via double writing param no longer works
  8. 8. Confirm critical InLong functionalities (data ingestion, sorting, clustering) operate normally
Caveat Major version upgrade from 1.x to 2.x may include breaking changes; review Apache InLong 2.1.0 release notes for migration details

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Inlong Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27531 — 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-2025-27531 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