VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libapache-mod-jk: vulnerability history, versions and safety

libapache-mod-jk is a package in the Debian ecosystem. Vulert records 15 vulnerabilities for it across 2 releases, from Mar 2007 to Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded U15
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 libapache-mod-jk vulnerabilities

Vulert verdict on libapache-mod-jk i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 15 vulnerabilities on record across 17 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 15 over 17 years · 0 in the last year i
  • Latest disclosure 14 Oct 2024 i
  • Highest CVSS 7.5 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 libapache-mod-jk, 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:1.2.48-1 U5 Yes Details →
1:1.2.48-1+deb11u1 U3 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 4
  • 2009 2
  • 2015 2
  • 2018 2
  • 2023 2
  • 2024 3

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

03 Vulnerabilities

Recorded vulnerabilities for libapache-mod-jk

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Authentication Bypass Vulnerability in libapache-mod-jk: CVE-2023-41081 7.5 high 1:1.2.48-1+deb11u1 13 Sep 2023
Apache Tomcat JK Connector Vulnerability in libapache-mod-jk: Path Normalization Flaw 7.5 high 1:1.2.46-1 31 Oct 2018
Critical Vulnerability in libapache-mod-jk: JkUnmount Rule Bypass N/A unrated 1:1.2.40+svn150520-1 21 Apr 2015
Critical Vulnerability in libapache-mod-jk: Directory Traversal Risk N/A unrated 1:1.2.23-1 25 May 2007
Sensitive Information Disclosure in libapache-mod-jk: Apache Tomcat Vulnerability N/A unrated 1:1.2.26-2.1 09 Apr 2009

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 libapache-mod-jk

Is libapache-mod-jk safe to use?

Vulert records 15 vulnerabilities for libapache-mod-jk in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 15 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 libapache-mod-jk have?

15 vulnerabilities are recorded for libapache-mod-jk in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 15 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 libapache-mod-jk vulnerabilities disclosed?

0 vulnerabilities were recorded for libapache-mod-jk in the last 12 months, and the oldest entry in this database dates to 04 Mar 2007. 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 libapache-mod-jk 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 libapache-mod-jk for upcoming vulnerabilities?

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