{"id":"CVE-2026-42791","aliases":["DEBIAN-CVE-2026-42791","EEF-CVE-2026-42791","EUVD-2026-32273","GHSA-cjxj-wj6x-3fff","RHSA-2026:63160","SUSE-SU-2026:22082-1","UBUNTU-CVE-2026-42791","USN-8901-1","openSUSE-SU-2026:10947-1","openSUSE-SU-2026:11559-1","openSUSE-SU-2026:20907-1"],"status":"published","title":"OCSP responder certificate validity period not checked in public_key","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","severity":{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00316,"percentile":0.24756,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-295","CWE-672"],"published":"2026-05-27T12:23:13Z","modified":"2026-10-28T02:30:25Z","fixes":[{"ecosystem":"Debian:13","package":"erlang","fixed_in":["1:27.3.4.1+dfsg-1+deb13u3"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"erlang","fixed_in":["1:27.3.4.12+dfsg-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"erlang","fixed_in":["1:27.3.4.6+dfsg-1ubuntu0.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:13","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:27.3.4.1+dfsg-1+deb13u3"}]}],"versions":["1:27.3.4.1+dfsg-1","1:27.3.4.1+dfsg-1+deb13u1","1:27.3.4.1+dfsg-1+deb13u2"]},{"source":"osv","ecosystem":"Debian:14","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:27.3.4.12+dfsg-1"}]}],"versions":["1:27.3.4.1+dfsg-1","1:27.3.4.10+dfsg-1","1:27.3.4.11+dfsg-1","1:27.3.4.11+dfsg-2","1:27.3.4.11+dfsg-3","1:27.3.4.11+dfsg-4","1:27.3.4.11+dfsg-5","1:27.3.4.11+dfsg-6","1:27.3.4.11+dfsg-7","1:27.3.4.3+dfsg-1","1:27.3.4.4+dfsg-1","1:27.3.4.6+dfsg-1","1:27.3.4.8+dfsg-1","1:27.3.4.9+dfsg-1"]},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-asn1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-common_test","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-compiler","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-crypto","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-debugger","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-dialyzer","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-diameter","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-edoc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-eldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-erl_interface","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-erts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-et","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-eunit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-examples","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-ftp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-gdb-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-inets","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-jinterface","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-megaco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-mnesia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-observer","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-odbc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-os_mon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-parsetools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-public_key","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-reltool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-runtime_tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-sasl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-snmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-ssh","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-stdlib","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-syntax_tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-tftp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-wx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"erlang27-xmerl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:27.3.4.17-1.hum1"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"27.1.3-160000.5.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"27.1.3-160000.5.1"}]}],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:27.3+dfsg-1ubuntu1","1:27.3+dfsg-1ubuntu1.1","1:27.3.4.1+dfsg-1","1:27.3.4.1+dfsg-1build1","1:27.3.4.1+dfsg-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:27.3.4.6+dfsg-1ubuntu0.2"}]}],"versions":["1:27.3.4.1+dfsg-1build1","1:27.3.4.3+dfsg-1","1:27.3.4.4+dfsg-1","1:27.3.4.6+dfsg-1","1:27.3.4.6+dfsg-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:16.b.3-dfsg-1ubuntu2.2+esm3"}]}],"versions":["1:16.b.1-dfsg-4ubuntu1","1:16.b.2-dfsg-1ubuntu1","1:16.b.2-dfsg-2ubuntu1","1:16.b.3-dfsg-1ubuntu1","1:16.b.3-dfsg-1ubuntu2","1:16.b.3-dfsg-1ubuntu2.1","1:16.b.3-dfsg-1ubuntu2.2","1:16.b.3-dfsg-1ubuntu2.2+esm1","1:16.b.3-dfsg-1ubuntu2.2+esm2"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:18.3-dfsg-1ubuntu3.1+esm4"}]}],"versions":["1:18.0-dfsg-1ubuntu1","1:18.0-dfsg-1ubuntu2","1:18.2-dfsg-2ubuntu1","1:18.3-dfsg-1ubuntu1","1:18.3-dfsg-1ubuntu2","1:18.3-dfsg-1ubuntu3","1:18.3-dfsg-1ubuntu3.1","1:18.3-dfsg-1ubuntu3.1+esm1","1:18.3-dfsg-1ubuntu3.1+esm2","1:18.3-dfsg-1ubuntu3.1+esm3"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:20.2.2+dfsg-1ubuntu2+esm4"}]}],"versions":["1:20.0.4+dfsg-1ubuntu1","1:20.1.2+dfsg-1ubuntu1","1:20.1.3+dfsg-1ubuntu1","1:20.1.4+dfsg-1ubuntu1","1:20.1.5+dfsg-1ubuntu1","1:20.1.6+dfsg-1ubuntu1","1:20.1.7+dfsg-1ubuntu1","1:20.2.1+dfsg-1ubuntu1","1:20.2.2+dfsg-1ubuntu1","1:20.2.2+dfsg-1ubuntu2","1:20.2.2+dfsg-1ubuntu2+esm1","1:20.2.2+dfsg-1ubuntu2+esm2","1:20.2.2+dfsg-1ubuntu2+esm3"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:22.2.7+dfsg-1ubuntu0.5+esm3"}]}],"versions":["1:22.0.7+dfsg-1build1","1:22.2+dfsg-1","1:22.2.1+dfsg-1","1:22.2.2+dfsg-1","1:22.2.3+dfsg-1","1:22.2.3+dfsg-2","1:22.2.4+dfsg-1","1:22.2.7+dfsg-1","1:22.2.7+dfsg-1ubuntu0.2","1:22.2.7+dfsg-1ubuntu0.3","1:22.2.7+dfsg-1ubuntu0.4","1:22.2.7+dfsg-1ubuntu0.5","1:22.2.7+dfsg-1ubuntu0.5+esm1","1:22.2.7+dfsg-1ubuntu0.5+esm2"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:24.2.1+dfsg-1ubuntu0.8"}]}],"versions":["1:23.2.6+dfsg-1build1","1:24.1.1+dfsg-1","1:24.1.4+dfsg-1","1:24.1.5+dfsg-1","1:24.1.5+dfsg-1ubuntu1","1:24.2+dfsg-1","1:24.2.1+dfsg-1","1:24.2.1+dfsg-1ubuntu0.1","1:24.2.1+dfsg-1ubuntu0.2","1:24.2.1+dfsg-1ubuntu0.3","1:24.2.1+dfsg-1ubuntu0.4","1:24.2.1+dfsg-1ubuntu0.5","1:24.2.1+dfsg-1ubuntu0.6","1:24.2.1+dfsg-1ubuntu0.7"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:25.3.2.8+dfsg-1ubuntu4.8"}]}],"versions":["1:25.2.3+dfsg-1","1:25.3.2.8+dfsg-1","1:25.3.2.8+dfsg-1ubuntu1","1:25.3.2.8+dfsg-1ubuntu3","1:25.3.2.8+dfsg-1ubuntu4","1:25.3.2.8+dfsg-1ubuntu4.1","1:25.3.2.8+dfsg-1ubuntu4.2","1:25.3.2.8+dfsg-1ubuntu4.3","1:25.3.2.8+dfsg-1ubuntu4.4","1:25.3.2.8+dfsg-1ubuntu4.5","1:25.3.2.8+dfsg-1ubuntu4.6","1:25.3.2.8+dfsg-1ubuntu4.7"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:27.3.4.6+dfsg-1ubuntu0.2"}]}],"versions":["1:27.3.4.1+dfsg-1build1","1:27.3.4.3+dfsg-1","1:27.3.4.4+dfsg-1","1:27.3.4.6+dfsg-1","1:27.3.4.6+dfsg-1ubuntu0.1"],"bundled":30},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"erlang27","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"27.1.3-2.1"}]}],"bundled":14},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"28.5.0.4-1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"erlang","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"27.1.3-160000.5.1"}]}],"bundled":5}],"products":[{"vendor":"erlang","product":"erlang\\/otp"},{"vendor":"erlang","product":"otp"}],"references":[{"url":"https://github.com/erlang/otp/security/advisories/GHSA-cjxj-wj6x-3fff","tags":["vendor-advisory","related","Mitigation","Vendor Advisory","advisory","article","report"]},{"url":"https://cna.erlef.org/cves/CVE-2026-42791.html","tags":["related","Third Party Advisory","web","article","report"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-42791","tags":["related","Third Party Advisory","web","article","report"]},{"url":"https://www.erlang.org/doc/system/versions.html#order-of-versions","tags":["x_version-scheme","Product","web","article","report"]},{"url":"https://github.com/erlang/otp/commit/7995f1fdaee3da569bb810358ce0f546471d169b","tags":["patch","Patch","fix","article","report"]},{"url":"https://github.com/erlang/otp/commit/b3870e02405c709a872b01ba6086065620cdfe76","tags":["patch","Patch","fix","article","report"]},{"url":"https://github.com","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/42xxx/CVE-2026-42791.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-42791","tags":["advisory"]},{"url":"https://github.com/erlang/otp","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-42791","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:63160","tags":["advisory"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-75538","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70405","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-55952","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-54891","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-54886","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-48860","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-48858","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-48855","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-42791","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-42790","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-42789","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-49759","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_63160.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2482093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-42789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-42789","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-42789.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/471cd2f664300a95353c467873800bbe706005db","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/59c8d824386b2eb1614ff9340624843ef6aca0fd","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-c99q-jmpx-v8qq","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-42789","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2482286","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-42790","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-42790","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-42790.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/0769050c69d73762672b0db1347b6993a5b31759","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/21abed64eb2026b5f82f432709e4e932f9be389a","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/fb67c6d1836f51105a96d8b769e71e4215a79457","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-22cw-4ph4-6447","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-42790","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2481950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-42791","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2487603","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-48855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48855","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-48855.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/8f4224a0d2676b0653d2c71a889a956e8c2c62d6","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-pv7g-pjrq-x2fh","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-48855","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2487593","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-48858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48858","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-48858.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/2691a806231ffd0490a8a9e20500dec0c7e73727","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/521bcfa24407ee8cb5614823cf905c37ea3aa605","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-24cv-hwgr-37fq","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-48858","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2487597","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-48860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48860","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-48860.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/0209a6df65d605552b378273027b3968b35f26b4","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-gp7x-mfv6-52cv","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-48860","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2487607","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-49759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49759","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-49759.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/3983d495284331c121f600a80bac9fcf4e16381e","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-6f4f-chj5-5g97","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-49759","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2496623","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-54886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-54886","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-54886.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/eaf9550b8ad4738b81149d3f617102d980c6dd18","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-7wp4-pc27-2vj9","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-54886","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2496625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-54891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-54891","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-54891.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/07d2d0e93f6aaf7652a81e8df075fc1728da5e96","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-gf6r-99xw-6qg6","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-54891","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2496626","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-55952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55952","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-55952.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/2c3e599797644310e5d4aa39c7193420e59dadff","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/9b5437c72fa3403a75c1aba28e5c532bc191c662","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/e77823e6d980b2ec0b4fe4ea3f2d098ca239e3ce","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-8c57-44c9-pc59","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-55952","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2526850","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70405","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-70405.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/aba0fe8c2d700bf4ac94607cf7f00e53bbe4042d","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/e3be1cfe9f6cedd0cd20d9905e05601dfb31c8aa","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-q7cq-pfgf-5hr7","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-70405","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2526856","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-75538","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-75538","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-75538.html","tags":["article"]},{"url":"https://github.com/erlang/otp/commit/08e8efdba8500d2d6f54c6b1de1492b228017c9b","tags":["article"]},{"url":"https://github.com/erlang/otp/security/advisories/GHSA-8m6r-2pj2-25pm","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-75538","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622082-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1244642","tags":["report"]},{"url":"https://bugzilla.suse.com/1262503","tags":["report"]},{"url":"https://bugzilla.suse.com/1266448","tags":["report"]},{"url":"https://bugzilla.suse.com/1266449","tags":["report"]},{"url":"https://bugzilla.suse.com/1266466","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-4748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-32147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42791","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-42791","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8901-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-4748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-26618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-30211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-21620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-28808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-28810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-32144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-32147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-42789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-42790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-48855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-48856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-48858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-48860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-49759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-49760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-54886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-54887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-54891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-55950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-55952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-65634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89422","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2025-48038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-48039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-21620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-28808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-28810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-32144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-47078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-49759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-49760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-58227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59251","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-42791","title":"OCSP responder certificate validity period not checked in public_key","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T12:23:13.584Z","modified":"2026-07-24T14:14:24.911Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium","assessor":"cna"}],"cwes":["CWE-295","CWE-672"],"updated_at":"2026-11-02T13:40:23.731501Z"}],"euvd":[{"id":"EUVD-2026-32273","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T12:23:13Z","modified":"2026-07-24T14:14:24Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium"}],"updated_at":"2026-11-02T18:19:40.671085Z"}],"nvd":[{"id":"CVE-2026-42791","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T14:16:53.46Z","modified":"2026-10-26T11:10:00.157Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low","assessor":"primary"}],"cwes":["CWE-295","CWE-672"],"updated_at":"2026-11-02T14:12:20.511562Z"}],"osv":[{"id":"CVE-2026-42791","title":"OCSP responder certificate validity period not checked in public_key","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T12:23:13.584Z","modified":"2026-10-28T02:30:25.48939668Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium"}],"cwes":["CWE-295","CWE-672"],"updated_at":"2026-11-02T15:45:04.117819Z"},{"id":"DEBIAN-CVE-2026-42791","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.  OCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.  This affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.  This issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T14:16:53.46Z","modified":"2026-10-27T09:47:38.586053806Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:45:55.251751Z"},{"id":"EEF-CVE-2026-42791","title":"OCSP responder certificate validity period not checked in public_key","description":"## Summary\n\nImproper Certificate Validation vulnerability in Erlang OTP public\\_key (pubkey\\_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid.\n\nOCSP response verification in pubkey\\_ocsp:verify\\_response/5 and pubkey\\_ocsp:is\\_authorized\\_responder/3 in lib/public\\_key/src/pubkey\\_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid.\n\nThis affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public\\_key:pkix\\_ocsp\\_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate.\n\nThis issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public\\_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.\n\n## Workarounds\n\n\\* For TLS clients using the ssl application, disable OCSP stapling by setting {stapling, no\\_staple} in the client options, or switch to CRL-based revocation checking with {crl\\_check, true}.\n\\* For applications calling public\\_key:pkix\\_ocsp\\_validate/5 directly, validate the responder certificate's validity period in application code before calling the function.\n\n## Configurations\n\nFor the ssl application, OCSP stapling must be enabled by setting the stapling option to staple in the TLS client options. OCSP stapling is not enabled by default.\n\nApplications calling public\\_key:pkix\\_ocsp\\_validate/5 directly are unconditionally affected when that function is used.","status":"published","published":"2026-05-27T12:23:13.584Z","modified":"2026-09-08T03:30:05.422892489Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium"}],"cwes":["CWE-295","CWE-672"],"updated_at":"2026-11-02T15:46:33.047032Z"},{"id":"RHSA-2026:63160","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-09T10:19:44Z","modified":"2026-10-20T10:43:33.918623083Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:21.91255Z"},{"id":"UBUNTU-CVE-2026-42791","description":"Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid. OCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid. This affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate. This issue affects OTP from OTP 27.0 before OTP 29.0.1, OTP 28.5.0.1 and OTP 27.3.4.12, corresponding to public_key from 1.16 before 1.21.1, 1.20.3.1 and 1.17.1.3.","status":"published","published":"2026-05-27T14:16:00Z","modified":"2026-10-08T19:47:10.138142198Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","level":"medium"},{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T16:56:18.393417Z"},{"id":"openSUSE-SU-2026:10947-1","title":"erlang27-27.1.3-2.1 on GA media","description":"These are all security issues fixed in the erlang27-27.1.3-2.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-06-03T00:00:00Z","modified":"2026-06-04T09:00:08.489232736Z","updated_at":"2026-11-02T16:58:38.95195Z"},{"id":"openSUSE-SU-2026:11559-1","title":"erlang-28.5.0.4-1.1 on GA media","description":"These are all security issues fixed in the erlang-28.5.0.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-20T00:00:00Z","modified":"2026-08-21T09:15:09.246696292Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:20907-1","title":"Security update for erlang","description":"This update for erlang fixes the following issues\n\n- CVE-2025-4748: improper limitation of a pathname may lead to path traversal (bsc#1244642).\n- CVE-2026-32147: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in SFTP chroot\n  (bsc#1262503).\n- CVE-2026-42789: `public_key` application accepts non-CA certificates as intermediate issuers and this enables chain\n  forgery (bsc#1266449).\n- CVE-2026-42790: Name Constraints and Subject CommonName fallback in TLS hostname verification allows for certificate\n  forgery by MITM attacker (bsc#1266466).\n- CVE-2026-42791: OCSP response verification in the `public_key` application does not check the validity period of the\n  OCSP responder certificate and allows for OCSP response response forgery (bsc#1266448).\n","status":"published","published":"2026-06-05T11:01:03Z","modified":"2026-06-09T18:24:31.025873668Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"SUSE-SU-2026:22082-1","title":"Security update for erlang","description":"This update for erlang fixes the following issues\n\n- CVE-2025-4748: improper limitation of a pathname may lead to path traversal (bsc#1244642).\n- CVE-2026-32147: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in SFTP chroot\n  (bsc#1262503).\n- CVE-2026-42789: `public_key` application accepts non-CA certificates as intermediate issuers and this enables chain\n  forgery (bsc#1266449).\n- CVE-2026-42790: Name Constraints and Subject CommonName fallback in TLS hostname verification allows for certificate\n  forgery by MITM attacker (bsc#1266466).\n- CVE-2026-42791: OCSP response verification in the `public_key` application does not check the validity period of the\n  OCSP responder certificate and allows for OCSP response response forgery (bsc#1266448).\n","status":"published","published":"2026-06-05T10:59:34Z","modified":"2026-06-16T18:24:37.610969319Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"USN-8901-1","title":"erlang vulnerabilities","description":"Wander Nauta discovered that Erlang incorrectly handled absolute paths when\nextracting zip archives. An attacker could possibly use this issue to write\narbitrary files outside of the intended directory. This issue only affected\nUbuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2025-4748)\n\nIt was discovered that the Erlang SFTP server did not properly limit the\nsize of packets. A remote attacker could possibly use this issue to cause\nErlang to use excessive resources, leading to a denial of service. This\nissue only affected Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, and\nUbuntu 18.04 LTS. (CVE-2025-26618)\n\nIt was discovered that the Erlang SSH server did not properly limit the\nlength of algorithm names in key exchange messages. A remote attacker could\npossibly use this issue to cause Erlang to use excessive resources, leading\nto a denial of service. This issue only affected Ubuntu 14.04 LTS,\nUbuntu 16.04 LTS, and Ubuntu 18.04 LTS. (CVE-2025-30211)\n\nIt was discovered that the Erlang TFTP server incorrectly handled certain\nfile paths. A remote attacker could possibly use this issue to access files\noutside of the intended directory. (CVE-2026-21620)\n\nIt was discovered that the Erlang SFTP server incorrectly validated paths\nagainst the configured root directory. An authenticated user could possibly\nuse this issue to access files outside of the root directory.\n(CVE-2026-23942)\n\nIt was discovered that the Erlang SSH server enabled zlib compression by\ndefault and did not limit the size of decompressed data. A remote attacker\ncould possibly use this issue to cause Erlang to use excessive resources,\nleading to a denial of service. (CVE-2026-23943)\n\nIt was discovered that the Erlang HTTP server incorrectly applied directory\naccess controls to CGI scripts served via script aliases. A remote attacker\ncould possibly use this issue to bypass authentication and access protected\nCGI scripts. (CVE-2026-28808)\n\nIt was discovered that the Erlang DNS resolver used predictable transaction\nIDs and did not randomize source ports. A remote attacker could possibly\nuse this issue to perform DNS cache poisoning attacks. This issue only\naffected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS.\n(CVE-2026-28810)\n\nIt was discovered that Erlang did not verify the signatures of designated\nOCSP responder certificates. A remote attacker could possibly use this\nissue to forge OCSP responses and bypass certificate revocation checks.\nThis issue only affected Ubuntu 26.04 LTS. (CVE-2026-32144)\n\nIt was discovered that the Erlang SFTP server incorrectly handled file\nattribute changes on open file handles. An authenticated user could\npossibly use this issue to modify the attributes of files outside of the\nroot directory. (CVE-2026-32147)\n\nIt was discovered that Erlang incorrectly allowed non-CA certificates to\nact as intermediate certificate issuers. A remote attacker could possibly\nuse this issue to forge certificate chains. (CVE-2026-42789)\n\nIt was discovered that Erlang incorrectly handled DNS name constraints\nduring hostname verification. A remote attacker could possibly use this\nissue to bypass certificate validation. This issue only affected\nUbuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and\nUbuntu 26.04 LTS. (CVE-2026-42790)\n\nIt was discovered that Erlang did not check the validity period of OCSP\nresponder certificates. A remote attacker could possibly use this issue to\nforge OCSP responses using an expired responder certificate. This issue\nonly affected Ubuntu 26.04 LTS. (CVE-2026-42791)\n\nIt was discovered that Erlang incorrectly handled relative paths when\nextracting zip archives. An attacker could possibly use this issue to write\narbitrary files outside of the intended directory. This issue only affected\nUbuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and\nUbuntu 26.04 LTS. (CVE-2026-47078)\n\nIt was discovered that the Erlang SFTP server exposed absolute paths when\nreading symbolic links. An authenticated user could possibly use this issue\nto obtain sensitive information. (CVE-2026-48855)\n\nIt was discovered that the Erlang HTTP client forwarded authorization\nheaders on cross-origin redirects. A malicious HTTP server could possibly\nuse this issue to obtain sensitive information. (CVE-2026-48856)\n\nIt was discovered that the Erlang FTP client did not validate the IP\naddress in passive mode responses. A malicious FTP server could possibly\nuse this issue to perform server-side request forgery attacks.\n(CVE-2026-48858)\n\nIt was discovered that Erlang checked the local address instead of the peer\naddress when enforcing the allowlist for distribution over TLS. A remote\nattacker could possibly use this issue to bypass access restrictions. This\nissue only affected Ubuntu 26.04 LTS. (CVE-2026-48860)\n\nIt was discovered that Erlang incorrectly handled certain SCTP ERROR\nchunks, leading to a buffer overflow. A remote attacker could possibly use\nthis issue to cause Erlang to crash, resulting in a denial of service.\n(CVE-2026-49759)\n\nIt was discovered that the Erlang erl_interface library incorrectly handled\nprinting very large integers, leading to a buffer overflow. An attacker\ncould possibly use this issue to cause Erlang to crash or execute arbitrary\ncode. (CVE-2026-49760)\n\nIt was discovered that the Erlang SFTP server incorrectly handled certain\npath resolution requests. An authenticated user could possibly use this\nissue to determine the existence of files outside of the root directory.\n(CVE-2026-53422)\n\nIt was discovered that the Erlang SFTP server incorrectly handled extended\nchannel data, leading to an infinite loop. An authenticated user could\npossibly use this issue to cause a denial of service. (CVE-2026-54886)\n\nIt was discovered that the Erlang DTLS server used a predictable cookie\nsecret on startup. A remote attacker could possibly use this issue to\nbypass source address verification. This issue only affected\nUbuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and\nUbuntu 26.04 LTS. (CVE-2026-54887)\n\nIt was discovered that Erlang TLS clients incorrectly accepted application\ndata before the handshake was completed. A remote attacker could possibly\nuse this issue to inject arbitrary data into TLS connections.\n(CVE-2026-54891)\n\nIt was discovered that the Erlang DTLS server contained a race condition\nwhen handling rapid client reconnections. A remote attacker could possibly\nuse this issue to cause Erlang to crash, resulting in a denial of service.\nThis issue only affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS.\n(CVE-2026-55950)\n\nIt was discovered that Erlang did not properly validate TLS 1.3 pre-shared\nkey extensions. A remote attacker could possibly use this issue to cause\nErlang to crash, resulting in a denial of service. This issue only affected\nUbuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS.\n(CVE-2026-55952)\n\nIt was discovered that the Erlang ASN.1 decoder incorrectly handled certain\nobject identifiers. A remote attacker could possibly use this issue to\ncause Erlang to use excessive resources, leading to a denial of service.\n(CVE-2026-65634)\n\nIt was discovered that the Erlang SSH server did not properly limit the\nnumber of open channels. An authenticated user could possibly use this\nissue to cause Erlang to use excessive resources, leading to a denial of\nservice. This issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS,\nUbuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS.\n(CVE-2026-68956)\n\nIt was discovered that the Erlang HTTP server incorrectly shared users and\ngroups between directories when using dets or mnesia authentication\nbackends. A remote attacker could possibly use this issue to bypass\nauthentication and access protected directories. (CVE-2026-74994)\n\nIt was discovered that Erlang TLS clients incorrectly accepted unsolicited\nTLS 1.3 pre-shared keys from servers. A remote attacker could possibly use\nthis issue to impersonate servers. This issue only affected\nUbuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS.\n(CVE-2026-89422)","status":"published","published":"2026-10-08T12:01:56Z","modified":"2026-10-08T19:58:53.589918012Z","updated_at":"2026-11-02T16:58:26.907654Z"}]}}