InlongApplication · Apache
CVE-2024-26580
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 · uneditedDeserialization of Untrusted Data vulnerability in Apache InLong.This issue affects Apache InLong: from 1.8.0 through 1.10.0, the attackers can use the specific payload to read from an arbitrary file. Users are advised to upgrade to Apache InLong's 1.11.0 or cherry-pick [1] to solve it. [1] https://github.com/apache/inlong/pull/9673
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 · high confidenceDeserialization of untrusted data vulnerability in Apache InLong versions 1.8.0 through 1.10.0 allows remote attackers to read arbitrary files on the server using a specific malicious payload. This critical vulnerability (CVSS 9.1) stems from insecure deserialization handling in the affected versions.
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
>= 1.4.0, < 1.11.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache InLong versionLocate the InLong installation directory and check the version file or pom.xml. Common locations: check the VERSION file in the root directory, or look for version in the compiled JAR manifest. Alternatively, query the /api/inlong/manager/version endpoint if the API is exposed.Affected if The installed version is 1.4.0 through 1.10.0 (any version >= 1.4.0 and < 1.11.0)
-
Verify deserialization endpoints are accessibleCheck network exposure of InLong API services. Look for exposed manager, dataproxy, or audit API ports (typically 8080, 8081). Identify if unauthenticated or weakly authenticated endpoints accept serialized data payloads.Affected if Deserialization input points are reachable over the network without additional authentication barriers
-
Inspect InLong data source configurationReview the configuration files in the InLong distribution under the conf/ directory. Specifically examine manager.properties, dataproxy.conf, and any data ingestion or connector configuration files that handle object deserialization.Affected if Configuration permits deserialization of data from untrusted network sources without validation
-
Check for custom deserialization transformersLook for any custom Java deserialization handlers, especially implementations of ObjectInputStream or similar deserialization interfaces in the classpath or configuration. Search for Kryo, Jackson XML, or other serialization libraries configured in the dataproxy or manager components.Affected if Custom or third-party deserialization transformers handle incoming data streams
You are affected if Apache InLong version is 1.4.0 through 1.10.0 and the system accepts deserialized data from untrusted sources over exposed network endpoints.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.11.0
Upgrade to Apache InLong 1.11.0 or apply the cherry-pick from GitHub PR #9673 to remediate the deserialization vulnerability.
1.11.0
- Backup your current InLong installation and all data
- Stop the InLong service
- Download Apache InLong version 1.11.0 from the official Apache repository
- Install version 1.11.0 following the standard upgrade procedure
- Verify the upgrade was successful by checking the version number
- Restart the InLong service
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Inlong
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26580 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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