{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-63039 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63039 is a critical SQL injection vulnerability in Apache InLong, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63039 and fix it if it is affected.\n\nWhat it is: CVE-2026-63039 is a critical SQL injection vulnerability in Apache InLong, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63039 in the wild and no public exploit code.\n\nAffected product: Apache InLong. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63039/ (Markdown: https://insights.sbomify.com/CVE-2026-63039/index.md)","id":"CVE-2026-63039","markdown":"https://insights.sbomify.com/CVE-2026-63039/index.md","name":"CVE-2026-63039","record":{"aliases":["GHSA-pg4r-4hvf-4rqh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache InLong","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via unvalidated input in AuditAlertRuleService, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"inlong","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache InLong. This allows an attacker to inject the string value into\nthe SQL statement, enabling SQL injection.\n\nThis issue affects Apache InLong: from 2.0.0 before 2.4.0.\n\nUsers are advised to upgrade to Apache InLong's  2.4.0 or cherry-pick [1] to solve it.\n\n[1]  https://github.com/apache/inlong/pull/12080 .","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-24","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-24T16:34:41Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-63039","stars":0,"title":"Reproducer for CVE-2026-63039 (Apache InLong AuditAlertRule MyBatis ORDER BY SQL injection via orderField/orderType)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService","id":"CVE-2026-63039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache InLong: Missing authorization in StreamSource forceDelete","id":"CVE-2026-63040"},"packages":[],"prev":{"headline":"Apache InLong: SQL Injection via String Concatenation Vulnerability Report","id":"CVE-2026-63038"},"products":["Apache InLong"],"published":"2026-08-20","related":[{"cvss_score":9.8,"headline":"Apache InLong: Unauthenticated SQL injection in Manager OpenAPI audit alert rule list endpoint","id":"CVE-2026-63037","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":9.8,"headline":"Apache InLong: SQL Injection via String Concatenation Vulnerability Report","id":"CVE-2026-63038","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":9.8,"headline":"Apache InLong: An arbitrary file read vulnerability for JDBC","id":"CVE-2025-27531","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":9.8,"headline":"Apache Inlong JDBC Vulnerability","id":"CVE-2024-26579","kev_date_added":null,"published":"2024-05-08"},{"cvss_score":9.8,"headline":"Apache InLong: Remote Code Execution vulnerability in Apache InLong Manager","id":"CVE-2023-51784","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":9.8,"headline":"Apache InLong: Jdbc Connection Security Bypass in InLong","id":"CVE-2023-43668","kev_date_added":null,"published":"2023-10-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-24","vendors":["Apache Software Foundation"]},"summary":"Attackers can execute arbitrary SQL commands via unvalidated input in AuditAlertRuleService, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2026-63039/"}