Analysis
Common Weaknesses
The most common CWE weakness classes across Erlang ecosystem CVEs
The chart below shows the most common weaknesses found in vulnerabilities across the Erlang ecosystem. Understanding which weakness types recur most often helps library authors and application developers focus their security efforts where they matter most.
Each CVE is mapped to its CWE (Common Weakness Enumeration) using the MITRE CWE hierarchy. A slice's count includes every CVE reachable anywhere below it in the hierarchy, not just CVEs assigned that exact CWE — click a slice or legend row to drill into its direct children and see the same breakdown one level down.
Insufficient Verification of Data Authenticity CWE-345 CWE-345 at MITRE
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CVEs
CVEs for Insufficient Verification of Data Authenticity CWE-345
| Summary | Publication | CVE ID | Published |
|---|---|---|---|
| Guardian.revoke/3 acts on unverified token claims, allowing forged-token session revocation | CVE-2026-55735 | 2026-08-01 | |
| Insufficient verification of Hex package metadata in Gleam |
Gleam
ghcr.io / gleam-lang/gleam
|
CVE-2026-59247 | 2026-07-29 |
| Plaintext APPLICATION_DATA injected during TLS handshake delivered to client application post-handshake in ssl |
Erlang
Erlang / ssl
|
CVE-2026-54891 | 2026-07-02 |
| gun HTTP/2 PUSH_PROMISE authority not validated against connection origin allows cross-origin cookie injection | CVE-2026-43972 | 2026-06-08 | |
| Lockfile checksums not verified in Hex allows dependency integrity bypass |
Hex Mix Integration
|
CVE-2026-32148 | 2026-04-30 |