p PatchFirst

CVE-2026-5246

CVE-2026-5246 · Cesanta Mongoose P-384 Public Key mongoose.c mg_tls_verify_cert_signature authorization

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

A vulnerability was determined in Cesanta Mongoose up to 7.20. Affected is the function mg_tls_verify_cert_signature of the file mongoose.c of the component P-384 Public Key Handler. Executing a manipulation can lead to authorization bypass. The attack can be executed remotely. Attacks of this nature are highly complex. The exploitability is told to be difficult. The exploit has been publicly disclosed and may be utilized. Upgrading to version 7.21 is able to address this issue. This patch is called 0d882f1b43ff2308b7486a56a9d60cd6dba8a3f1. The affected component should be upgraded. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

CVSS 6.3 · Medium · EPSS 0.6% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • mongoose

    Versions
    • 7.0: Affected
    • 7.1: Affected
    • 7.2: Affected
    • 7.3: Affected
    • 7.4: Affected
    • 7.5: Affected
    • 7.6: Affected
    • 7.7: Affected
    • 7.8: Affected
    • 7.9: Affected
    • 7.10: Affected
    • 7.11: Affected
    • 7.12: Affected
    • 7.13: Affected
    • 7.14: Affected
    • 7.15: Affected
    • 7.16: Affected
    • 7.17: Affected
    • 7.18: Affected
    • 7.19: Affected
    • 7.20: Affected
    • 7.21: Not affected

    Update to 7.21

  • swupdate Debian:12

    Versions
    • 2022.12+dfsg-4
    • 2022.12+dfsg-4+deb12u1
    • 2022.12+dfsg-4+deb12u1~bpo11+1
    • 2022.12+dfsg-4+deb12u2
    • 2023.05+dfsg-1
    • 2023.05+dfsg-2
    • 2023.05+dfsg-2~bpo12+1
    • 2023.05+dfsg-3
    • 2023.05+dfsg-4
    • 2023.05+dfsg-5
    • 2023.05+dfsg-5~bpo12+1
    • 2023.12+dfsg-1
    • 2023.12+dfsg-1~bpo12+1
    • 2023.12.1+dfsg-1
    • 2023.12.1+dfsg-1~bpo12+1
    • 2023.12.1+dfsg-2
    • 2023.12.1+dfsg-2~bpo12+1
    • 2024.05+dfsg-1
    • 2024.05.2+dfsg-1
    • 2024.05.2+dfsg-2
    • 2024.05.2+dfsg-2~bpo12+1
    • 2024.12+dfsg-1
    • 2024.12+dfsg-2
    • 2024.12+dfsg-2~bpo12+1
    • 2024.12.1+dfsg-1
    • 2024.12.1+dfsg-1~bpo12+1
    • 2024.12.1+dfsg-2
    • 2024.12.1+dfsg-3
    • 2024.12.1+dfsg-3~bpo12+1
    • 2025.05+dfsg-1
    • 2025.05+dfsg-2
    • 2025.05+dfsg-2~bpo13+1
    • 2025.05+dfsg-3
    • 2025.05+dfsg-3~bpo13+1
    • 2025.12+dfsg-1
    • 2025.12+dfsg-10
    • 2025.12+dfsg-10~bpo13+1
    • 2025.12+dfsg-10~bpo13+2
    • 2025.12+dfsg-2
    • 2025.12+dfsg-2~bpo13+1
    • 2025.12+dfsg-3
    • 2025.12+dfsg-4
    • 2025.12+dfsg-5
    • 2025.12+dfsg-6
    • 2025.12+dfsg-7
    • 2025.12+dfsg-7~bpo13+1
    • 2025.12+dfsg-8
    • 2025.12+dfsg-9
    • 2026.05+dfsg-1
    • 2026.05+dfsg-2
    • 2026.05+dfsg-3
    • 2026.05+dfsg-3~bpo13+1
    • 2026.05+dfsg-4
    • 2026.05.1+dfsg-1
    • 2026.05.1+dfsg-1~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Debian:13

    Versions
    • 2024.12.1+dfsg-3
    • 2024.12.1+dfsg-3+deb13u1
    • 2024.12.1+dfsg-3+deb13u2
    • 2025.05+dfsg-1
    • 2025.05+dfsg-2
    • 2025.05+dfsg-2~bpo13+1
    • 2025.05+dfsg-3
    • 2025.05+dfsg-3~bpo13+1
    • 2025.12+dfsg-1
    • 2025.12+dfsg-10
    • 2025.12+dfsg-10~bpo13+1
    • 2025.12+dfsg-10~bpo13+2
    • 2025.12+dfsg-2
    • 2025.12+dfsg-2~bpo13+1
    • 2025.12+dfsg-3
    • 2025.12+dfsg-4
    • 2025.12+dfsg-5
    • 2025.12+dfsg-6
    • 2025.12+dfsg-7
    • 2025.12+dfsg-7~bpo13+1
    • 2025.12+dfsg-8
    • 2025.12+dfsg-9
    • 2026.05+dfsg-1
    • 2026.05+dfsg-2
    • 2026.05+dfsg-3
    • 2026.05+dfsg-3~bpo13+1
    • 2026.05+dfsg-4
    • 2026.05.1+dfsg-1
    • 2026.05.1+dfsg-1~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Debian:14

    Versions
    • 2024.12.1+dfsg-3
    • 2025.05+dfsg-1
    • 2025.05+dfsg-2
    • 2025.05+dfsg-2~bpo13+1
    • 2025.05+dfsg-3
    • 2025.05+dfsg-3~bpo13+1
    • 2025.12+dfsg-1
    • 2025.12+dfsg-10~bpo13+1
    • 2025.12+dfsg-10~bpo13+2
    • 2025.12+dfsg-2
    • 2025.12+dfsg-2~bpo13+1
    • 2025.12+dfsg-3
    • 2025.12+dfsg-4
    • 2025.12+dfsg-5
    • 2025.12+dfsg-6
    • 2025.12+dfsg-7
    • 2025.12+dfsg-7~bpo13+1
    • 2025.12+dfsg-8
    • 2025.12+dfsg-9
    Affected ranges
    • ECOSYSTEM: < 2025.12+dfsg-10

    Update to 2025.12+dfsg-10

  • swupdate Ubuntu:22.04:LTS

    Versions
    • 2020.11-2
    • 2021.04-1.1
    • 2021.04-2
    • 2021.04-2build1
    • 2021.11-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Ubuntu:24.04:LTS

    Versions
    • 2023.05+dfsg-3
    • 2023.05+dfsg-4
    • 2023.05+dfsg-4build1
    • 2023.05+dfsg-5
    • 2023.12+dfsg-1
    • 2023.12.1+dfsg-1ubuntu1
    • 2023.12.1+dfsg-1ubuntu4
    • 2023.12.1+dfsg-1ubuntu5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Ubuntu:25.10

    Versions
    • 2024.12.1+dfsg-1build2
    • 2024.12.1+dfsg-2
    • 2024.12.1+dfsg-3
    • 2025.05+dfsg-2ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Ubuntu:26.10

    Versions
    • 2025.12+dfsg-4ubuntu1
    • 2026.05+dfsg-3ubuntu2
    • 2026.05+dfsg-4ubuntu1
    • 2026.05.1+dfsg-1ubuntu1
    • 2026.05.1+git20261001+dfsg-1ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • swupdate Ubuntu:26.04:LTS

    Versions
    • 2025.05+dfsg-2ubuntu1
    • 2025.05+dfsg-3ubuntu1
    • 2025.12+dfsg-1ubuntu1
    • 2025.12+dfsg-2ubuntu1
    • 2025.12+dfsg-3ubuntu1
    • 2025.12+dfsg-4ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →