CVE Intelligence
Low

CVE-2026-116137 — adm-zip through 0.6.1 Duplicate-Entry Validation Bypass via Canonically Equivalent Names

adm-zip through 0.6.1 contains a duplicate-entry validation bypass that allows attackers to evade the readEntries() check by using canonically equivalent entry names like './hello.txt' and 'hello.txt'. Attackers can craft ZIP archives where getEntry() or readAsText() validates benign content while extractAllTo() writes malicious content to the same path, bypassing integrity checks.

Published Oct 25, 2026 · Updated Oct 25, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.26%
ahead of 17% of scored CVEs · Oct 27, 2026
Affects
Cthackers
Adm-zip
CVSS base
3.7
Low · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Cthackers Adm-zip).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Cthackers Adm-zip ≤ 0.6.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.3 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
6.3 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
3.7 CVSS 3.1 Low 2.2 1.4 disclosure@vulncheck.com via NIST National Vulnerability Database
3.7 CVSS 3.1 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-436

Other CVEs with this weakness →

EPSS over time FIRST

Oct 26, 2026 → Oct 27, 2026 · 2 reading(s) · max 0.26%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · cthackers/adm-zip
    Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 25, 2026
  • CVSS changed · 3.7
    Oct 25, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 25, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 25, 2026 · Alertas do Telegram
  • CVE published
    Oct 25, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 25, 2026 – Oct 25, 2026
  • 1× Official description updated · Oct 25, 2026 – Oct 25, 2026

References

6 on the record

Elsewhere on this site

Cthackers
every CVE for this vendor
CWE-436
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114103 adm-zip 0.6.0 Decompression Bomb Guard Bypass via getDataAsync() 7d
  • CVE-2026-114104 adm-zip before 0.6.1 Duplicate ZIP Entry Name Validation Bypass 7d
  • CVE-2026-114105 Adm-zip before 0.6.1 Privilege Escalation via keepOriginalPermission Setuid Bits 7d
  • CVE-2026-114102 adm-zip before 0.6.1 Denial of Service via inflateAsync Unhandled Error Event 7d
  • CVE-2026-102282 adm-zip extraction preserves SUID/SGID bits from untrusted ZIPs -> local privilege escalation 23d
  • CVE-2026-77301 adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS) Sep 18, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-116137 is "adm-zip through 0.6.1 Duplicate-Entry Validation Bypass via Canonically Equivalent Names", rated Low. It affects Adm-zip (Cthackers); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.7 describes technical severity. EPSS 0.26% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.