# Apache InLong: JDBC Vulnerability for Invisible Character Bypass Leading to Arbitrary File Read

Advisory record · `GHSA-98v7-xxxv-hcrh`

- **Identifiers:** `GHSA-98v7-xxxv-hcrh` · `CVE-2025-27528`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 28 May 2025
- **Updated:** 28 May 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2025, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.inlong:manager-pojo` (Maven): affected `>=1.13.0, <2.2.0`; fixed in `2.2.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache InLong's manager-pojo package (Maven org.apache.inlong:manager-pojo) is affected in versions 1.13.0 through 2.1.0. The source describes a JDBC security bypass that leads to arbitrary file reading, but it gives few details about the attack conditions or required access. Upgrade to version 2.2.0 to fix the issue.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0086, the 59th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-98v7-xxxv-hcrh)

## Sources

- [GitHub Advisory Database: GHSA-98v7-xxxv-hcrh](https://github.com/advisories/GHSA-98v7-xxxv-hcrh)
- [OSV: GHSA-98v7-xxxv-hcrh](https://osv.dev/vulnerability/GHSA-98v7-xxxv-hcrh)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-27528>
- <https://github.com/apache/inlong/pull/11747>
- <https://github.com/apache/inlong>
- <https://lists.apache.org/thread/b807rqzgyv4qgvxw3nhkq8tl6g90gqgj>
- <http://www.openwall.com/lists/oss-security/2025/05/28/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-98v7-xxxv-hcrh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-98v7-xxxv-hcrh/>. Everything for agents: <https://agentprime.io/llms.txt>.