p PatchFirst

CVE-2026-42791

CVE-2026-42791 · OCSP responder certificate validity period not checked in public_key

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 6.3 · Medium · EPSS 0.3% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • erlang

    Versions
    • ≥ 1.16: Affected; ≥ 1.17.1.3: Not affected; ≥ 1.20.3.1: Not affected; ≥ 1.21.1: Not affected (otp)

    Update to 1.17.1.3

  • erlang

    Versions
    • ≥ 27.0: Affected; ≥ 27.3.4.12: Not affected; ≥ 28.5.0.1: Not affected; ≥ 29.0.1: Not affected (otp)
    • ≥ 2b1a742c651b90f8a7a1fb2ddde73f29915ea376: Affected; ≥ 7995f1fdaee3da569bb810358ce0f546471d169b: Not affected; ≥ b3870e02405c709a872b01ba6086065620cdfe76: Not affected (git)

    Update to 27.3.4.12

  • erlang Debian:13

    Versions
    • 1:27.3.4.1+dfsg-1
    • 1:27.3.4.1+dfsg-1+deb13u1
    • 1:27.3.4.1+dfsg-1+deb13u2
    Affected ranges
    • ECOSYSTEM: < 1:27.3.4.1+dfsg-1+deb13u3

    Update to 1:27.3.4.1+dfsg-1+deb13u3

  • erlang Debian:14

    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
    Affected ranges
    • ECOSYSTEM: < 1:27.3.4.12+dfsg-1

    Update to 1:27.3.4.12+dfsg-1

  • erlang Ubuntu:25.10

    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
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • erlang Ubuntu:26.04:LTS

    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
    Affected ranges
    • ECOSYSTEM: < 1:27.3.4.6+dfsg-1ubuntu0.2

    Update to 1:27.3.4.6+dfsg-1ubuntu0.2

Original sources

Check your server →