BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-42790High confidence

nameConstraints DNS bypass via subject CommonName fallback in public_key hostname verification

Erlang · OTP

Official source article: GitHub GHSA-22CW-4PH4-6447 ↗. Check the applicable product and release in the original source.

7.6HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.47% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Erlang OTP and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceerlangVendor fix publishedDebian records a fixed source-package version for this release.1:27.3.4.1+dfsg-1+deb13u3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceerlangAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceerlangVendor fix publishedDebian records a fixed source-package version for this release.1:27.3.4.12+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceerlangVendor fix publishedDebian records a fixed source-package version for this release.1:27.3.4.12+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveerlangUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-42790 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityerlang: Erlang OTP public_key: Certificate validation bypass allows hostname spoofing
20 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • erlang-asn1 as a component of Red Hat OpenStack Platform 17.1
  • erlang-compiler as a component of Red Hat OpenStack Platform 17.1
  • erlang-crypto as a component of Red Hat OpenStack Platform 17.1
  • erlang-eldap as a component of Red Hat OpenStack Platform 17.1
  • erlang-erts as a component of Red Hat OpenStack Platform 17.1
  • erlang-inets as a component of Red Hat OpenStack Platform 17.1
  • erlang-kernel as a component of Red Hat OpenStack Platform 17.1
  • erlang-mnesia as a component of Red Hat OpenStack Platform 17.1
  • erlang-os_mon as a component of Red Hat OpenStack Platform 17.1
  • erlang-parsetools as a component of Red Hat OpenStack Platform 17.1
  • erlang-public_key as a component of Red Hat OpenStack Platform 17.1
  • erlang-runtime_tools as a component of Red Hat OpenStack Platform 17.1
Summary
A flaw was found in Erlang OTP public_key. This improper certificate validation vulnerability allows a subordinate Certificate Authority (CA) with restricted DNS nameConstraints to bypass these restrictions. By issuing a leaf certificate that lacks a Subject Alternative Name (SAN) but contains a crafted CommonName (CN), an attacker can trick an Erlang OTP TLS client into accepting it as valid for an out-of-scope hostname. This can lead to hostname spoofing and potential man-in-the-middle attacks, compromising the integrity and confidentiality of communications.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-32558

No EUVD known-exploited evidence

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.6 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

What

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-295
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-32558Official EUVD mapping

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1719Erlang/OTP: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Erlang/OTP ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0796Multiples vulnérabilités dans Tenable Identity Exposure

d?id=CVE-2026-42764 Référence CVE CVE-2026-42765 https://www.cve.org/CVERecord?id=CVE-2026-42765 Référence CVE CVE-2026-42766 https://www.cve.org/CVERecord?id=CVE-2026-42766 Référence CVE CVE-2026-42767 https://www.cve.org/CVERecord?id=CVE-2026-42767 Référence CVE CVE-2026-42768 https://www.cve.org/CVERecord?id=CVE-2026-42768 Référence CVE CVE-2026-42769 https://www.cve.org/CVERecord?id=CVE-2026-42769 Référence CVE CVE-2026-42770 https://www.cve.org/CVERecord?id=CVE-2026-42770 Référence CVE CVE-2026-42771 https://www.cve.org/CVERecord?id=CVE-2026-42771 Référence CVE CVE-2026-42789 https://www.cve.org/CVERecord?id=CVE-2026-42789 Référence CVE CVE-2026-42790 https://www.cve.org/CVERecord?id=CVE-2026-42790 Référence CVE CVE-2026-42899 https://www.cve.org/CVERecord?id=CVE-2026-42899 Référence CVE CVE-2026-45445 https://www.cve.org/CVERecord?id=CVE-2026-45445 Référence CVE CVE-2026-45446 https://www.cve.org/CVERecord?id=CVE-2026-45446 Référence CVE CVE-2026-45447 https://www.cve.org/CVERecord?id=CVE-2026-45447 Référence CVE CVE-2026-45490 https://www.cve.org/CVERecord?id=CVE-2026-45490 Référence CVE CVE-2026-45491 https://www.cve.org/CVERecord?id=CVE-2026-45491 Référence CVE CVE-2026-45591 https://www.cve.org/CVERecord?id=CVE-2026-45591 Référence CVE CVE-2026-4873 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0731Multiples vulnérabilités dans les produits Microsoft

mai 2026 Bulletin de sécurité Microsoft CVE-2026-46227 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46229 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46230 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46231 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46233 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46234 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46236 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46238 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2025-15649 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-42789 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-42790 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-48962 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-48959 du 02 juin 2026 Bulletin de sécurité Microsoft CVE-2026-50031 du 04 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46273 du 05 juin 2026 Bulletin de sécurité Microsoft CVE-2026-50292 du 06 juin 2026 Bulletin de sécurité Microsoft CVE-2026-26142 du 09 juin 2026 Bulletin de sécurité Microsoft CVE-2026-33113 du 09 juin 2026 Bulletin de sécurité Microsoft CVE-2026-40371 du 09 juin 2026 Bulletin de sécurité Microsoft CVE-2026-40376 du 09 juin 2026 Bulletin de sécurité Microsoft CVE-2026-42835 du 09 juin 2026 Bulletin de séc

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-017841ERLANGのErlang/OTPにおける複数の脆弱性

Erlang OTPのpublic_key（pubkey_certおよびpublic_keyモジュール）には、不適切な証明書検証の脆弱性があります。この脆弱性により、TLSホスト名検証でsubject CommonNameにフォールバックすることでDNS nameConstraintsをバイパス可能です。2つの欠陥が組み合わさることで、DNS nameConstraintsで制限されている（例：permitted;DNS:allowed.example.com）サブオーディネートCAが、OTP TLSクライアントに範囲外のホスト名（例：victim.example.com）を有効なIDとして受け入れさせるリーフ証明書を発行できてしまいます。まず、lib/public_key/src/pubkey_cert.erl内のpubkey_cert:validate_names/6は、SANのDNSエントリのみをnameConstraintsと照合します。RFC 5280によれば、許可されたDNSサブツリーはDNS型の名前を含む証明書のみを制限します。subjectAltNameを持たないリーフ証明書は、そのsubject CommonNameに関係なく任意のpermitted;DNS:...制約を簡単に満たしてしまいます。次に、lib/public_key/src/public_key.erlのpublic_key:pkix_verify_hostname/3は、subjectAltNameが存在しない場合にsubject CommonNameにフォールバックし、id-at-commonName属性を提示されたIDとして抽出し、参照ホスト名と照合します。厳密なpkix_verify_hostname_match_fun(https)マッチャーでもこのフォールバックは抑制されません。その結果、SANを持たないためDNS制約が発動しないDNS制約付き中間CAの下で、CNのみのリーフ証明書が検証を通過し、ホスト名検証もCNフォールバックによりこれを受け入れてしまいます。このバイパスはverify_peer付きの標準ssl:connect、信頼済みCA、SNI、および正規の厳格なhttpsホスト名マッチャーを使用した場合に到達可能です。この問題はOTP 19.3からOTP 26.2.5.21、27.3.4.12、28.5.0.1、29.0.1のpublic_key 1.4から1.15.1.7、1.17.1.3、1.20.3.1、1.21.1に該当します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 27 May 2026 · Last source change 18 Sept 2026, 12:04 UTC · CWE-295 · Improper Certificate Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-32558
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    erlang27.src as a component of Red Hat Hardened Images; erlang-asn1 as a component of Red Hat OpenStack Platform 17.1; erlang-compiler as a component of Red Hat OpenStack Platform 17.1; erlang-crypto as a component of Red Hat OpenStack Platform 17.1; erlang-eldap as a component of Red Hat OpenStack Platform 17.1; erlang-erts as a component of Red Hat OpenStack Platform 17.1; erlang-inets as a component of Red Hat OpenStack Platform 17.1; erlang-kernel as a component of Red Hat OpenStack Platform 17.1; erlang-mnesia as a component of Red Hat OpenStack Platform 17.1; erlang-os_mon as a component of Red Hat OpenStack Platform 17.1; erlang-parsetools as a component of Red Hat OpenStack Platform 17.1; erlang-public_key as a component of Red Hat OpenStack Platform 17.1; erlang-runtime_tools as a component of Red Hat OpenStack Platform 17.1; erlang-sasl as a component of Red Hat OpenStack Platform 17.1; erlang-snmp as a component of Red Hat OpenStack Platform 17.1; erlang-ssl as a component of Red Hat OpenStack Platform 17.1; erlang-stdlib as a component of Red Hat OpenStack Platform 17.1; erlang-syntax_tools as a component of Red Hat OpenStack Platform 17.1; erlang-tools as a component of Red Hat OpenStack Platform 17.1; erlang-xmerl as a component of Red Hat OpenStack Platform 17.1; erlang.src as a component of Red Hat OpenStack Platform 17.1 · Fixed: erlang-0:23.3.4.18-2.el8ost.src as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-mnesia-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; and 61 more
    After
    erlang-asn1 as a component of Red Hat OpenStack Platform 17.1; erlang-compiler as a component of Red Hat OpenStack Platform 17.1; erlang-crypto as a component of Red Hat OpenStack Platform 17.1; erlang-eldap as a component of Red Hat OpenStack Platform 17.1; erlang-erts as a component of Red Hat OpenStack Platform 17.1; erlang-inets as a component of Red Hat OpenStack Platform 17.1; erlang-kernel as a component of Red Hat OpenStack Platform 17.1; erlang-mnesia as a component of Red Hat OpenStack Platform 17.1; erlang-os_mon as a component of Red Hat OpenStack Platform 17.1; erlang-parsetools as a component of Red Hat OpenStack Platform 17.1; erlang-public_key as a component of Red Hat OpenStack Platform 17.1; erlang-runtime_tools as a component of Red Hat OpenStack Platform 17.1; erlang-sasl as a component of Red Hat OpenStack Platform 17.1; erlang-snmp as a component of Red Hat OpenStack Platform 17.1; erlang-ssl as a component of Red Hat OpenStack Platform 17.1; erlang-stdlib as a component of Red Hat OpenStack Platform 17.1; erlang-syntax_tools as a component of Red Hat OpenStack Platform 17.1; erlang-tools as a component of Red Hat OpenStack Platform 17.1; erlang-xmerl as a component of Red Hat OpenStack Platform 17.1; erlang.src as a component of Red Hat OpenStack Platform 17.1 · Fixed: erlang-0:23.3.4.18-2.el8ost.src as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-mnesia-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; and 140 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.4 < *; 19.3 < *; b0c245e8132bb13171e277b1af59c0cec00c9459 < * · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    OTP: 1.4 < *, 19.3 < *, b0c245e8132bb13171e277b1af59c0cec00c9459 < * · Fixed: RHSA-2026:54757: Red Hat OpenStack Platform 16.2
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    erlang-asn1 as a component of Red Hat OpenStack Platform 17.1; erlang-compiler as a component of Red Hat OpenStack Platform 17.1; erlang-crypto as a component of Red Hat OpenStack Platform 17.1; erlang-eldap as a component of Red Hat OpenStack Platform 17.1; erlang-erts as a component of Red Hat OpenStack Platform 17.1; erlang-inets as a component of Red Hat OpenStack Platform 17.1; erlang-kernel as a component of Red Hat OpenStack Platform 17.1; erlang-mnesia as a component of Red Hat OpenStack Platform 17.1; erlang-os_mon as a component of Red Hat OpenStack Platform 17.1; erlang-parsetools as a component of Red Hat OpenStack Platform 17.1; erlang-public_key as a component of Red Hat OpenStack Platform 17.1; erlang-runtime_tools as a component of Red Hat OpenStack Platform 17.1; erlang-sasl as a component of Red Hat OpenStack Platform 17.1; erlang-snmp as a component of Red Hat OpenStack Platform 17.1; erlang-ssl as a component of Red Hat OpenStack Platform 17.1; erlang-stdlib as a component of Red Hat OpenStack Platform 17.1; erlang-syntax_tools as a component of Red Hat OpenStack Platform 17.1; erlang-tools as a component of Red Hat OpenStack Platform 17.1; erlang-xmerl as a component of Red Hat OpenStack Platform 17.1 · Fixed: erlang-0:23.3.4.18-2.el8ost.src as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-mnesia-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; and 61 more
    After
    erlang27.src as a component of Red Hat Hardened Images; erlang-asn1 as a component of Red Hat OpenStack Platform 17.1; erlang-compiler as a component of Red Hat OpenStack Platform 17.1; erlang-crypto as a component of Red Hat OpenStack Platform 17.1; erlang-eldap as a component of Red Hat OpenStack Platform 17.1; erlang-erts as a component of Red Hat OpenStack Platform 17.1; erlang-inets as a component of Red Hat OpenStack Platform 17.1; erlang-kernel as a component of Red Hat OpenStack Platform 17.1; erlang-mnesia as a component of Red Hat OpenStack Platform 17.1; erlang-os_mon as a component of Red Hat OpenStack Platform 17.1; erlang-parsetools as a component of Red Hat OpenStack Platform 17.1; erlang-public_key as a component of Red Hat OpenStack Platform 17.1; erlang-runtime_tools as a component of Red Hat OpenStack Platform 17.1; erlang-sasl as a component of Red Hat OpenStack Platform 17.1; erlang-snmp as a component of Red Hat OpenStack Platform 17.1; erlang-ssl as a component of Red Hat OpenStack Platform 17.1; erlang-stdlib as a component of Red Hat OpenStack Platform 17.1; erlang-syntax_tools as a component of Red Hat OpenStack Platform 17.1; erlang-tools as a component of Red Hat OpenStack Platform 17.1; erlang-xmerl as a component of Red Hat OpenStack Platform 17.1; erlang.src as a component of Red Hat OpenStack Platform 17.1 · Fixed: erlang-0:23.3.4.18-2.el8ost.src as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-asn1-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-compiler-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-crypto-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-debugsource-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-eldap-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erl_interface-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-erts-debuginfo-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-hipe-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-inets-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; erlang-kernel-0:23.3.4.18-2.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.2; erlang-mnesia-0:23.3.4.18-2.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.2; and 61 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-32558↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-22CW-4PH4-6447↗Mitigation reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-42790 · cve.blacktree.nl