CVE-2026-63015 Apache InLong: Non-template responsible persons can view template information
Unauthorized users can view template information in Apache InLong due to missing authorization checks, exposing sensitive data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-63015?
CVE-2026-63015 is a medium-severity missing authorization vulnerability in Apache InLong, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Uncontrolled Resource Consumption vulnerability in Apache InLong. Non-template responsible persons can view template information.
This issue affects Apache InLong: from 2.0.0 before 2.4.0.
Users are advised to upgrade to Apache InLong's 2.4.0 or cherry-pick [1] to solve it.
[1]
https://github.com/apache/inlong/pull/12093 https://github.com/apache/inlong/pull/11732
Weakness: CWE-400
Which versions are affected by CVE-2026-63015?
It affects 1 product.
Products include Apache Inlong.
How do I fix CVE-2026-63015?
No fix has been published for CVE-2026-63015 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-63015 being exploited?
There is no known exploitation of CVE-2026-63015 in the wild and no public exploit code.
Other vulnerabilities in Apache InLong
- CVE-2026-63037 Apache InLong: Unauthenticated SQL injection in Manager OpenAPI audit alert rule list endpoint
- CVE-2026-63038 Apache InLong: SQL Injection via String Concatenation Vulnerability Report
- CVE-2026-63039 Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService
- CVE-2025-27531 Apache InLong: An arbitrary file read vulnerability for JDBC
- CVE-2024-26579 Apache Inlong JDBC Vulnerability
Sources
Also known as GHSA-2wf7-pq8q-vp44.