Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A brass padlock and a rolled-up dollar bill rest on a silver computer keyboard.
    Photo by Sasun Bughdaryan on Unsplash

    OpenSSL advisory 20261117 fixes a Suite B TLS 1.3 read overrun and a PEM use-after-free

    Automated source check

    OpenSSL

    OpenSSL advisory fixes a Suite B server read overrun

    OpenSSL's advisory dated 20261117 covers two flaws that few deployments will reach: CVE-2026-35190 and CVE-2026-107493. CVE-2026-35190 lets a remote client send a ClientHello that makes a TLS 1.3 server with the Suite B certificate flag read past the end of a static array (CWE-125, out-of-bounds read). Its severity is medium.

    No memory contents are disclosed. On sanitizer or hardened-allocator builds the process may crash, which makes it a denial of service. In ordinary release builds the read covers a few bytes of neighbouring constant data, and those bytes are never sent back to the client.

    Why a client offering only X25519 triggers the read

    With the Suite B flag set, OpenSSL limits accepted groups to P-256 and P-384 by swapping in a fixed two-element list for the configured one. The key-share selection code was not updated for that swap. A ClientHello whose supported_groups and key_share hold no Suite B group, for example only X25519, forces the server to walk every configured tuple, and the read runs past the array. By default there are eight groups.

    The second flaw: a use-after-free in PEM_X509_INFO_read_bio_ex()

    CVE-2026-107493 is a use-after-free (CWE-416) in PEM_X509_INFO_read_bio_ex(), which loads certificates, CRLs and private keys from PEM data into a stack of X509_INFO structures. If the read fails, OpenSSL frees every entry in a stack the caller supplied but leaves the entries in it. Using that stack afterwards can crash the program and, in principle, corrupt memory.

    Malformed PEM data, such as an item with invalid content, can make the read fail. An attacker cannot make an application pass in an existing stack. PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex() run the same code.

    Check whether your code sets Suite B or reuses a PEM stack

    For CVE-2026-35190, you are exposed only if an application calls SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leaves TLS 1.3 on. Default configurations never reach the code. The stock openssl s_server -suiteB_128 command is not vulnerable, because it sets an X.509 verification parameter instead.

    The command comes from the documentation listed under Sources; check it against your own build before running it. For CVE-2026-107493, you are exposed only if your code passes a non-NULL stack to the function and keeps using it after a failed read. OpenSSL itself always passes NULL, including when TLS loads CA certificates, and the source expects very few applications to pass an existing stack.

    Neither record states affected version ranges. Exploitation status is unknown, as the sources do not say.

    No fixed OpenSSL version numbers are published in the records

    Neither record names a fixed release. The advisory at https://openssl-library.org/news/secadv/20261117.txt is where to look for one, and the NVD record for CVE-2026-35190 lists fix commits 9491b0d9cc79, 9a812981b927 and ade64619df04. For CVE-2026-107493 the listed commits are 0486dfadfec5, c57a5ccf0c06 and c8f6d04f8e6d. Update once the advisory points to a release for your branch.

    Until then, avoid the affected pattern: skip the Suite B flag on TLS 1.3 servers, and do not touch a caller-supplied stack after a failed PEM read. Neither flaw affects the FIPS module, since the code sits outside its boundary.

    Sources

    Image: Photo by Sasun Bughdaryan on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion