VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.twelvemonkeys.imageio:imageio-metadata: vulnerability history, versions and safety

com.twelvemonkeys.imageio:imageio-metadata is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 24 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
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 com.twelvemonkeys.imageio:imageio-metadata vulnerabilities

Vulert verdict on com.twelvemonkeys.imageio:imageio-metadata 3.15.3 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.15.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 19 packages i
  • Stars 2,151 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence non-standard 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 com.twelvemonkeys.imageio:imageio-metadata, 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
3.15.3 06 Oct 2026 none non-standard — Details →
3.15.2 18 Sep 2026 none non-standard — Details →
3.15.1 15 Sep 2026 none non-standard — Details →
3.15.0 06 Sep 2026 none non-standard — Details →
3.14.0 14 Jul 2026 none non-standard — Details →
3.13.1 22 Feb 2026 none non-standard — Details →
3.13.0 22 Dec 2025 none non-standard — Details →
3.12.0 07 Oct 2024 none non-standard — Details →
3.11.0 08 Jun 2024 none non-standard — Details →
3.10.1 07 Nov 2023 none non-standard — Details →
3.10.0 20 Oct 2023 none non-standard — Details →
3.9.4 21 Nov 2022 none non-standard — Details →
3.9.3 20 Oct 2022 none non-standard — Details →
3.9.2 20 Oct 2022 none non-standard — Details →
3.9.1 19 Oct 2022 none non-standard — Details →
3.9.0 15 Oct 2022 none non-standard — Details →
3.8.3 19 Aug 2022 none non-standard — Details →
3.8.2 22 Feb 2022 none non-standard — Details →
3.8.1 27 Dec 2021 none non-standard — Details →
3.8.0 12 Dec 2021 none non-standard — Details →
3.7.1 11 Dec 2021 none non-standard — Details →
3.7.0 24 Apr 2021 C1 non-standard Yes Details →
3.6.4 08 Mar 2021 C1 non-standard Yes Details →
3.6.3 26 Feb 2021 C1 non-standard Yes Details →
3.6.2 23 Jan 2021 C1 non-standard Yes Details →
3.6.1 20 Nov 2020 C1 non-standard Yes Details →
3.6 10 Jul 2020 C1 non-standard Yes Details →
3.5 22 Jan 2020 C1 non-standard Yes Details →
3.4.3 09 Jan 2020 C1 non-standard Yes Details →
3.4.2 12 Aug 2019 C1 non-standard Yes Details →
3.4.1 07 Sep 2018 C1 non-standard Yes Details →
3.4 18 Aug 2018 C1 non-standard Yes Details →
3.3.2 02 Feb 2017 C1 non-standard Yes Details →
3.3.1 29 Nov 2016 C1 non-standard Yes Details →
3.3 02 Nov 2016 C1 non-standard Yes Details →
3.2.1 11 Dec 2015 C1 — Yes Details →
3.2 01 Nov 2015 C1 — Yes Details →
3.1.2 14 Aug 2015 C1 — Yes Details →
3.1.1 11 Jun 2015 C1 — Yes Details →
3.1.0 10 Apr 2015 C1 — Yes Details →
3.0.2 03 Jan 2015 C1 — Yes Details →
3.0.1 28 Nov 2014 C1 — Yes Details →
3.0 01 Oct 2014 C1 — Yes Details →
3.0-rc7 01 Oct 2014 C1 — Yes Details →
3.0-rc5 15 Feb 2014 C1 — Yes Details →

All 45 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 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.twelvemonkeys.imageio:imageio-metadata

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-23792: External Entity Reference in TwelveMonkeys ImageIO 9.8 critical 3.7.1 07 May 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 com.twelvemonkeys.imageio:imageio-metadata

Is com.twelvemonkeys.imageio:imageio-metadata safe to use?

Vulert records 1 vulnerabilities for com.twelvemonkeys.imageio:imageio-metadata in Maven: 1 critical, 0 high, 0 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 com.twelvemonkeys.imageio:imageio-metadata's Vulert package health score?

Vulert scores com.twelvemonkeys.imageio:imageio-metadata 82/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 com.twelvemonkeys.imageio:imageio-metadata affected?

No. 3.15.3, 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.

Which version of com.twelvemonkeys.imageio:imageio-metadata should I use?

3.15.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.twelvemonkeys.imageio:imageio-metadata have?

1 vulnerability is recorded for com.twelvemonkeys.imageio:imageio-metadata in the Maven ecosystem: 1 critical, 0 high, 0 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 com.twelvemonkeys.imageio:imageio-metadata vulnerabilities disclosed?

0 vulnerabilities were recorded for com.twelvemonkeys.imageio:imageio-metadata in the last 12 months, and the oldest entry in this database dates to 07 May 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 com.twelvemonkeys.imageio:imageio-metadata 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 com.twelvemonkeys.imageio:imageio-metadata for upcoming vulnerabilities?

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