VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

tecnickcom/tcpdf: vulnerability history, versions and safety

tecnickcom/tcpdf is a package in the Packagist ecosystem. Vulert records 10 vulnerabilities for it across 120 releases, from Oct 2022 to Dec 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C1 H2 M7
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 tecnickcom/tcpdf vulnerabilities

Vulert verdict on tecnickcom/tcpdf i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 2 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 10 over 2 years · 0 in the last year i
  • Latest disclosure 27 Dec 2024 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 tecnickcom/tcpdf, 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
6.7.8 H2 M4 Yes Details →
6.7.7 H2 M4 Yes Details →
6.7.6 H2 M4 Yes Details →
6.7.5 H2 M5 Yes Details →
6.7.4 H2 M6 Yes Details →
6.6.2 H2 M7 Yes Details →
6.6.1 H2 M7 Yes Details →
6.6.0 H2 M7 Yes Details →
6.5.0 H2 M7 Yes Details →
6.4.4 H2 M7 Yes Details →
6.4.3 H2 M7 Yes Details →
6.4.2 H2 M7 Yes Details →
6.4.1 H2 M7 Yes Details →
6.3.5 H2 M7 Yes Details →
6.3.4 H2 M7 Yes Details →
6.3.3 H2 M7 Yes Details →
6.3.2 H2 M7 Yes Details →
6.3.1 H2 M7 Yes Details →
6.3.0 H2 M7 Yes Details →
6.2.26 H2 M7 Yes Details →
6.2.25 H2 M7 Yes Details →
6.2.23 H2 M7 Yes Details →
6.2.22 H2 M7 Yes Details →
6.2.21 C1 H2 M7 Yes Details →
6.2.20 C1 H2 M7 Yes Details →
6.2.19 C1 H2 M7 Yes Details →
6.2.17 C1 H2 M7 Yes Details →
6.2.16 C1 H2 M7 Yes Details →
6.2.13 C1 H2 M7 Yes Details →
6.2.12 C1 H2 M7 Yes Details →
6.2.11 C1 H2 M7 Yes Details →
6.2.10 C1 H2 M7 Yes Details →
6.2.9 C1 H2 M7 Yes Details →
6.2.8 C1 H2 M7 Yes Details →
6.2.7 C1 H2 M7 Yes Details →
6.2.6 C1 H2 M7 Yes Details →
6.2.5 C1 H2 M7 Yes Details →
6.2.4 C1 H2 M7 Yes Details →
6.2.3 C1 H2 M7 Yes Details →
6.2.2 C1 H2 M7 Yes Details →
6.2.1 C1 H2 M7 Yes Details →
6.2.0 C1 H2 M7 Yes Details →
6.1.1 C1 H2 M7 Yes Details →
6.1.0 C1 H2 M7 Yes Details →
6.0.099 C1 H2 M7 Yes Details →
6.0.098 C1 H2 M7 Yes Details →
6.0.097 C1 H2 M7 Yes Details →
6.0.096 C1 H2 M7 Yes Details →
6.0.095 C1 H2 M7 Yes Details →
6.0.094 C1 H2 M7 Yes Details →
6.0.093 C1 H2 M7 Yes Details →
6.0.092 C1 H2 M7 Yes Details →
6.0.091 C1 H2 M7 Yes Details →
6.0.090 C1 H2 M7 Yes Details →
6.0.089 C1 H2 M7 Yes Details →
6.0.088 C1 H2 M7 Yes Details →
6.0.087 C1 H2 M7 Yes Details →
6.0.086 C1 H2 M7 Yes Details →
6.0.085 C1 H2 M7 Yes Details →
6.0.084 C1 H2 M7 Yes Details →
6.0.083 C1 H2 M7 Yes Details →
6.0.082 C1 H2 M7 Yes Details →
6.0.081 C1 H2 M7 Yes Details →
6.0.080 C1 H2 M7 Yes Details →
6.0.079 C1 H2 M7 Yes Details →
6.0.078 C1 H2 M7 Yes Details →
6.0.077 C1 H2 M7 Yes Details →
6.0.076 C1 H2 M7 Yes Details →
6.0.075 C1 H2 M7 Yes Details →
6.0.074 C1 H2 M7 Yes Details →
6.0.073 C1 H2 M7 Yes Details →
6.0.072 C1 H2 M7 Yes Details →
6.0.071 C1 H2 M7 Yes Details →
6.0.070 C1 H2 M7 Yes Details →
6.0.069 C1 H2 M7 Yes Details →
6.0.068 C1 H2 M7 Yes Details →
6.0.067 C1 H2 M7 Yes Details →
6.0.066 C1 H2 M7 Yes Details →
6.0.065 C1 H2 M7 Yes Details →
6.0.064 C1 H2 M7 Yes Details →
6.0.063 C1 H2 M7 Yes Details →
6.0.062 C1 H2 M7 Yes Details →
6.0.061 C1 H2 M7 Yes Details →
6.0.060 C1 H2 M7 Yes Details →
6.0.059 C1 H2 M7 Yes Details →
6.0.058 C1 H2 M7 Yes Details →
6.0.057 C1 H2 M7 Yes Details →
6.0.056 C1 H2 M7 Yes Details →
6.0.055 C1 H2 M7 Yes Details →
6.0.054 C1 H2 M7 Yes Details →
6.0.053 C1 H2 M7 Yes Details →
6.0.052 C1 H2 M7 Yes Details →
6.0.051 C1 H2 M7 Yes Details →
6.0.050 C1 H2 M7 Yes Details →
6.0.049 C1 H2 M7 Yes Details →
6.0.048 C1 H2 M7 Yes Details →
6.0.047 C1 H2 M7 Yes Details →
6.0.046 C1 H2 M7 Yes Details →
6.0.045 C1 H2 M7 Yes Details →
6.0.044 C1 H2 M7 Yes Details →
6.0.043 C1 H2 M7 Yes Details →
6.0.042 C1 H2 M7 Yes Details →
6.0.041 C1 H2 M7 Yes Details →
6.0.040 C1 H2 M7 Yes Details →
6.0.039 C1 H2 M7 Yes Details →
6.0.038 C1 H2 M7 Yes Details →
6.0.037 C1 H2 M7 Yes Details →
6.0.036 C1 H2 M7 Yes Details →
6.0.035 C1 H2 M7 Yes Details →
6.0.034 C1 H2 M7 Yes Details →
6.0.033 C1 H2 M7 Yes Details →
6.0.032 C1 H2 M7 Yes Details →
6.0.031 C1 H2 M7 Yes Details →
6.0.030 C1 H2 M7 Yes Details →
6.0.029 C1 H2 M7 Yes Details →
6.0.028 C1 H2 M7 Yes Details →
6.0.027 C1 H2 M7 Yes Details →
6.0.026 C1 H2 M7 Yes Details →
6.0.025 C1 H2 M7 Yes Details →
6.0.024 C1 H2 M7 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 9

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

03 Vulnerabilities

Recorded vulnerabilities for tecnickcom/tcpdf

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2018-17057: TCPDF vulnerable to attackers triggering deserialization of arbitrary data 9.8 critical 6.2.22 06 Oct 2022
CVE-2024-56521: TCPDF Package Suffers from Insecure Certificate Validation 8.2 high 6.8.0 27 Dec 2024
CVE-2024-56522: TCPDF Incorrect Comparison Vulnerability 7.5 high 6.8.0 27 Dec 2024
CVE-2024-51058: TCPDF Local File Inclusion Vulnerability 6.2 medium 6.7.6 26 Nov 2024
TCPDF Cross-site Scripting vulnerability in tecnickcom/tcpdf 6.1 medium 6.7.4 15 Apr 2024

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 tecnickcom/tcpdf

Is tecnickcom/tcpdf safe to use?

Vulert records 10 vulnerabilities for tecnickcom/tcpdf in Packagist: 1 critical, 2 high, 7 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.

How many vulnerabilities does tecnickcom/tcpdf have?

10 vulnerabilities are recorded for tecnickcom/tcpdf in the Packagist ecosystem: 1 critical, 2 high, 7 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 tecnickcom/tcpdf vulnerabilities disclosed?

0 vulnerabilities were recorded for tecnickcom/tcpdf in the last 12 months, and the oldest entry in this database dates to 06 Oct 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 tecnickcom/tcpdf 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 tecnickcom/tcpdf for upcoming vulnerabilities?

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