CVE-2026-4046: iconv crash due to assertion failure with untrusted input
The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application.
This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4046 is an availability flaw in GNU glibc iconv. An application that converts untrusted input using IBM1390 or IBM1399 character sets may crash. This is a denial-of-service risk, not a data theft or code execution issue based on the provided sources.
Executive priority
Treat as high priority for availability-sensitive and internet-facing systems. The business risk is service disruption, especially in systems that parse external content. Patch or disable unused character sets through normal emergency-change processes.
Technical view
glibc iconv in versions 2.43 and earlier can hit an assertion failure during IBM1390 or IBM1399 conversion, mapped to CWE-617. The CVSS 3.1 score is 7.5 because the reported impact is network-reachable, unauthenticated, low-complexity availability loss.
Likely exposure
Exposure is most likely where Linux services use glibc iconv on attacker-controlled content or attacker-selected encodings and IBM1390/IBM1399 converters are installed. Systems not using those character sets have a straightforward mitigation path.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The stated risk is remote application crash when a reachable application processes untrusted input through the affected character set conversions.
Researcher notes
The source bundle has inconsistent affected-version metadata, but the description and glibc advisory state versions 2.43 and earlier. No exploit code, patch diff analysis, or active exploitation evidence is included here.
Mitigation direction
Check GNU glibc and operating-system vendor advisories for fixed packages.
Remove IBM1390 and IBM1399 character sets where they are not needed.
Prioritize internet-facing services that process uploaded text, mail, documents, or user-selected encodings.
Apply vendor updates after compatibility testing.
Review Siemens advisory if affected Siemens products are in scope.
Validation and detection
Inventory glibc versions on Linux servers and appliances.
Check whether IBM1390 or IBM1399 conversion modules are installed or enabled.
Identify applications calling iconv on untrusted input or user-selected encodings.
Confirm vendor patches or charset removal in staging before production rollout.
Review service logs for unexplained assertion failures or crashes in text conversion paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-617 · source CWE mapping
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.