InlongApplication · Apache
CVE-2024-26579
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.7.0 through 1.11.0, the attackers can bypass using malicious parameters. Users are advised to upgrade to Apache InLong's 1.12.0 or cherry-pick [1], [2] to solve it. [1] https://github.com/apache/inlong/pull/9694 [2] https://github.com/apache/inlong/pull/9707
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 confidenceApache InLong versions 1.7.0 through 1.11.0 contain a deserialization vulnerability where attackers can bypass security controls using malicious parameters. This allows remote code execution or arbitrary command execution by sending crafted serialized data to vulnerable deserialization endpoints.
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.7.0, < 1.12.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache InLong installationLocate InLong deployment by checking for inlong-manager service, looking for InLong installation directories, or querying running processes (ps aux | grep inlong)Affected if Apache InLong is present in the environment
-
Determine installed InLong versionCheck the version by examining the pom.xml in the InLong source, the manager service startup logs, or querying the management API endpoint /api/inlong/manager/version if availableAffected if Installed version is >= 1.7.0 and < 1.12.0
-
Identify exposed deserialization endpointsReview InLong manager service configuration files (application.yml or application.properties) for exposed REST API endpoints, particularly those handling serialized data or object inputAffected if Deserialization endpoints are accessible without additional authentication layers
-
Check network exposure of InLong servicesReview firewall rules, security groups, and proxy configurations to determine if InLong manager API ports (typically 8080 or 8081) are exposed to untrusted networksAffected if InLong services are reachable from untrusted network segments
User is affected if Apache InLong version is 1.7.0 through 1.11.0 and the deserialization endpoints are network-accessible.
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.12.0
Upgrade to Apache InLong version 1.12.0 or apply the cherry-picks from PRs #9694 and #9707 to remediate the insecure deserialization vulnerability.
1.12.0
- Upgrade Apache InLong from version 1.7.0-1.11.0 to version 1.12.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Inlong
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26579 — 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-26579 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