VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.xmlgraphics:batik: vulnerability history, versions and safety

org.apache.xmlgraphics:batik is a package in the Maven ecosystem. Vulert records 9 vulnerabilities for it across 7 releases, from Feb 2022 to Oct 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded C1 H5 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.xmlgraphics:batik vulnerabilities

Vulert verdict on org.apache.xmlgraphics:batik 1.20 i

Updated on 22 Oct 2026

Good news: 1.20, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 9.

Package health score 74/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

What to do: Stay on 1.20 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.20 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.20 — unaffected i
  • Vulnerabilities on record 9 over 1 year · 0 in the last year i
  • Latest disclosure 25 Oct 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 248 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.xmlgraphics:batik, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.20 20 Oct 2026 none Apache-2.0 — Details →
1.19 06 May 2025 none Apache-2.0 — Details →
1.18 09 Oct 2024 none Apache-2.0 — Details →
1.17 21 Aug 2023 none Apache-2.0 — Details →
1.16 14 Oct 2022 none Apache-2.0 — Details →
1.15 15 Sep 2022 H2 Apache-2.0 Yes Details →
1.14 12 Jan 2021 H3 M2 Apache-2.0 Yes Details →
1.13 05 May 2020 H3 M2 Apache-2.0 Yes Details →
1.12 25 Oct 2019 H4 M2 Apache-2.0 Yes Details →
1.11 01 Feb 2019 H4 M2 Apache-2.0 Yes Details →
1.10 11 May 2018 H4 M2 Apache-2.0 Yes Details →
1.9.1 25 Jul 2017 C1 H4 M2 Apache-2.0 Yes Details →

All 12 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.xmlgraphics:batik

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-8013: Apache Batik - Deserialization of Untrusted Data 9.8 critical 1.10 13 May 2022
CVE-2019-17566: Server-side request forgery (SSRF) in Apache Batik 7.5 high 1.13 09 Feb 2022
CVE-2022-40146: Apache Batik Server-Side Request Forgery 7.5 high 1.15 23 Sep 2022
CVE-2022-41704: Apache XML Graphics Batik Code Execution via SVG 7.5 high 1.16 25 Oct 2022
CVE-2022-42890: Untrusted code execution in Apache XML Graphics Batik 7.5 high 1.16 25 Oct 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.xmlgraphics:batik

Is org.apache.xmlgraphics:batik safe to use?

Vulert records 9 vulnerabilities for org.apache.xmlgraphics:batik in Maven: 1 critical, 5 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.xmlgraphics:batik's Vulert package health score?

Vulert scores org.apache.xmlgraphics:batik 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.xmlgraphics:batik affected?

No. 1.20, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does org.apache.xmlgraphics:batik have?

9 vulnerabilities are recorded for org.apache.xmlgraphics:batik in the Maven ecosystem: 1 critical, 5 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.xmlgraphics:batik vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.xmlgraphics:batik in the last 12 months, and the oldest entry in this database dates to 09 Feb 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.xmlgraphics:batik are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.xmlgraphics:batik for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.xmlgraphics:batik version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.