Yes. fooman/tcpdf (Packagist): upgrade to 6.2.22 or later; la-haute-societe/tcpdf (Packagist): upgrade to 6.2.22 or later; spoonity/tcpdf (Packagist): upgrade to 6.2.22 or later; tecnickcom/tcpdf (Packagist): upgrade to 6.2.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-17057?
Check whether you run fooman/tcpdf (Packagist), la-haute-societe/tcpdf (Packagist), spoonity/tcpdf (Packagist) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
fooman/tcpdf (Packagist): upgrade to 6.2.22 or later
composer require fooman/tcpdf:^6.2.22
la-haute-societe/tcpdf (Packagist): upgrade to 6.2.22 or later
composer require la-haute-societe/tcpdf:^6.2.22
spoonity/tcpdf (Packagist): upgrade to 6.2.22 or later
composer require spoonity/tcpdf:^6.2.22
tecnickcom/tcpdf (Packagist): upgrade to 6.2.22 or later