Threats Tagged 'cve-2026-16517'
View all threats tagged with 'cve-2026-16517'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-16517'
Click on any threat for detailed analysis and mitigation recommendations
A signed integer overflow vulnerability exists in libarchive's ZIP writer when ZIP encryption is enabled and the entry file size is near the maximum 64-bit integer value. This overflow can cause undefined behavior such as incorrect Zip64 extension decisions or potential memory corruption. The vulnerability is rated low severity by Red Hat due to the highly contrived conditions required for exploitation and limited impact. A security update for Red Hat Hardened Images RPMs including libarchive packages addresses this issue. Join the discussion | GCVE Database | 07/22/2026, 18:12:39 UTC Added: 09/22/2026, 02:04:02 UTC |
0 A signed integer overflow vulnerability was found in libarchive's ZIP writer. In the archive_write_zip_header function in archive_write_set_format_zip.c, when ZIP encryption is enabled and the entry file size is close to INT64_MAX, the addition of the encryption overhead to the entry size overflows int64_t, resulting in undefined behavior. This could lead to incorrect Zip64 extension decisions or potential memory corruption. Join the discussion | GCVE Database | 07/22/2026, 00:32:36 UTC Added: 07/22/2026, 23:24:25 UTC |
0 A signed integer overflow vulnerability was found in libarchive's ZIP writer. In the archive_write_zip_header function in archive_write_set_format_zip.c, when ZIP encryption is enabled and the entry file size is close to INT64_MAX, the addition of the encryption overhead to the entry size overflows int64_t, resulting in undefined behavior. This could lead to incorrect Zip64 extension decisions or potential memory corruption. Join the discussion | CVE Database V5 | 07/21/2026, 22:41:38 UTC Added: 07/21/2026, 23:07:49 UTC |
Showing 1 to 3 of 3 results