Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-63044: CWE-918 Server-Side Request Forgery (SSRF) in Apache Software Foundation Apache InLong

0
High
VulnerabilityCVE-2026-63044cvecve-2026-63044cwe-918
Published: 08/20/2026 (08/20/2026, 15:57:02 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache InLong

Description

Apache InLong versions from 2.0.0 up to but not including 2.4.0 contain a Server-Side Request Forgery (SSRF) vulnerability. This flaw allows any authenticated user, without requiring admin privileges, to make the InLong Manager server perform outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. The vulnerability is addressed in version 2.4.0 and later.

Affected software

GitHub Actionsmore threats →ai
apache/inlong
pkg:github/apache/inlong
Affected versions
=2.0.0<2.4.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/20/2026, 16:22:33 UTC

Technical Analysis

CVE-2026-63044 is a Server-Side Request Forgery (SSRF) vulnerability in Apache InLong affecting versions >=2.0.0 <2.4.0. It permits any authenticated user, regardless of role, to induce the InLong Manager server to initiate outbound HTTP or TCP connections to arbitrary internal network hosts and ports. This could potentially be leveraged to access internal resources not otherwise accessible to the user. The issue is fixed in Apache InLong version 2.4.0, with a patch available via the referenced pull request.

Potential Impact

An attacker with any authenticated access can exploit this SSRF vulnerability to make the server connect to arbitrary internal network addresses and ports. This may allow unauthorized access to internal services or network scanning from the server's perspective. No evidence of active exploitation is reported. The impact depends on the internal network configuration and what services are reachable from the InLong Manager server.

Mitigation Recommendations

Users should upgrade Apache InLong to version 2.4.0 or later to remediate this vulnerability. Alternatively, they can apply the patch referenced in the official pull request (https://github.com/apache/inlong/pull/12130). No other mitigation guidance is provided. Patch status is confirmed by vendor advisory information.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-07-15T07:08:41.577Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a87265dacd9273b49d54f61

Added to database: 08/20/2026, 16:07:57 UTC

Last enriched: 08/20/2026, 16:22:33 UTC

Last updated: 08/20/2026, 16:56:21 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses