CVE Intelligence
Medium Input validation

CVE-2016-10228 — The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with...

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

Published Mar 1, 2017 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

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 4.1% (30-day exploitation probability)+14
  • Technical severity (medium)+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
4.11%
ahead of 91% of scored CVEs · Oct 14, 2026
Affects
Gnu
Glibc
CVSS base
5.9
Medium · 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 (Gnu Glibc).
  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. EPSS ahead of 91% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Gnu Glibc ≤ 2.25 Vulnerable NIST National Vulnerability Database

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
None
Availability
High

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
5.9 CVSS 3.0 Medium 2.2 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.9 CVSS 3.0 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 4.11%

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
  • Record published
    Oct 14, 2026
  • Affected products added · gnu/glibc
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.9
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2017
  • CVE published
    Mar 1, 2017 · mitre

Source activity

Repeated readings are counted rather than listed.

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

References

14 on the record

Elsewhere on this site

Gnu
every CVE for this vendor
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-6238 Buffer overread in ns_printrrf with corrupted RDATA field Apr 28, 2026
  • High CVE-2026-5435 Potential buffer overflow in ns_sprintrrf TSIG handling path Apr 28, 2026
  • High CVE-2026-5928 Potential buffer under-read in ungetwc Apr 20, 2026
  • Critical CVE-2026-5450 scanf %mc off-by-one heap buffer overflow Apr 20, 2026
  • High CVE-2026-4046 iconv crash due to assertion failure with untrusted input Mar 30, 2026
  • Medium CVE-2026-4438 gethostbyaddr and gethostbyaddr_r return invalid DNS hostnames Mar 20, 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-2016-10228 is "The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with...", rated Medium. It affects Glibc (Gnu); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 4.11% 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.