VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

batik: vulnerability history, versions and safety

batik is a package in the Debian ecosystem. Vulert records 28 vulnerabilities for it across 3 releases, from Mar 2005 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded U28
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 batik vulnerabilities

Vulert verdict on batik i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 20 Jul 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 28 vulnerabilities on record across 20 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 28 over 20 years · 0 in the last year i
  • Latest disclosure 20 Jul 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

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 holds for batik, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.12-4 U18 Yes Details →
1.12-4+deb11u2 U9 Yes Details →
1.12-4+deb11u1 U13 Yes Details →

Newest 3 of 3 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2005 2
  • 2015 2
  • 2017 2
  • 2018 2
  • 2020 2
  • 2021 2
  • 2022 11
  • 2023 4
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for batik

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Deserialization Vulnerability in Apache Batik: CVE-2018-8013 9.8 critical 1.10-1 24 May 2018
Server-Side Request Forgery in Apache Batik 1.13: A Critical Vulnerability 8.2 high 1.12-4+deb11u3 24 Feb 2021
Server-Side Request Forgery Vulnerability in Apache Batik 7.5 high 1.12-1.1 12 Nov 2020
Critical Java Code Execution Vulnerability in Apache Batik 7.5 high 1.12-4+deb11u1 25 Oct 2022
Server-Side Request Forgery (SSRF) Vulnerability in Apache XML Graphics Batik 7.5 high 1.12-4+deb11u3 22 Sep 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 batik

Is batik safe to use?

Vulert records 28 vulnerabilities for batik in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 28 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does batik have?

28 vulnerabilities are recorded for batik in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 28 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new batik vulnerabilities disclosed?

0 vulnerabilities were recorded for batik in the last 12 months, and the oldest entry in this database dates to 14 Mar 2005. 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 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 batik for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the 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.