High, CVSS 8.2npmAmendedPublished
exiftool-vendored vulnerable to argument injection via newline characters in tag names
CVE-2026-43893 · GHSA-cw26-7653-2rp5
- Affected
- npm exiftool-vendored <= 35.18.0
- Fixed in
- 35.19.0· Vendor fix available
- Issue
- Impact exiftool-vendored starts ExifTool in -stayopen True -@ - mode, where arguments are read from stdin one per line. In affected versions, several caller-supplied strings were interpolated into ExifTool arguments without rejecting line delimiters. A newline or carriage return inside one of those strings could split a single intended argument into multiple ExifTool arguments, allowing argument injection. The fix also rejects NUL bytes as unsafe control characters. Applications that pass attacker-controlled strings to affected APIs may allow an attacker to make ExifTool read files accessible to the ExifTool process, or write output to attacker-chosen file system paths accessible to that process. No remote code execution has been demonstrated. The reported write-path issue is caused by unsanitized tag keys. Tag values passed to ExifTool#write are not affected, because WriteTask already encodes whitespace characters in values (e.g. \n - ) before transmission. Confirmed affected…
Recommended action: Upgrade to 35.19.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.