Is org.apache.inlong:manager-pojo 2.1 vulnerable?

Maven · 1 release from 2.1.0 to 2.1.0 · latest org.apache.inlong:manager-pojo is 2.4.0 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. org.apache.inlong:manager-pojo 2.1.0, the last 2.1 release, is affected by 3 known security advisories (1 high, 2 medium), including CVE-2025-27522, CVE-2025-27526, CVE-2025-27528. Upgrade to 2.2.0 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.inlong:manager-pojo -DdepVersion=2.2.0 -DforceVersion=true

Is your project on an affected org.apache.inlong:manager-pojo?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting org.apache.inlong:manager-pojo 2.1.0

  • MediumCVE-2025-27526GHSA-532x-j9r7-8f7328 May 2025

    Apache InLong: JDBC Vulnerability For URLEncode and backspace bypass

    Affected
    >=1.13.0 <2.2.0
    Fixed in
    2.2.0
  • MediumCVE-2025-27528GHSA-98v7-xxxv-hcrh28 May 2025

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

    Affected
    >=1.13.0 <2.2.0
    Fixed in
    2.2.0
  • HighCVE-2025-27522GHSA-r324-vgr5-73c928 May 2025

    Apache InLong: JDBC Vulnerability during verification processing

    Affected
    >=1.13.0 <2.2.0
    Fixed in
    2.2.0

Which of your client projects are still on org.apache.inlong:manager-pojo 2.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.inlong:manager-pojo version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.inlong:manager-pojo versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.