By weakness (CWE)

CWE-757: related vulnerabilities

CVEs classified under CWE-757. Understanding the weakness class helps prioritize systemic fixes over one-off patches.

3 published vulnerabilities

  • CVE-2026-54291MEDIUM 5.9

    pgjdbc, the official PostgreSQL JDBC driver, contains a flaw in versions 42.7.4 through 42.7.11 where connections explicitly configured to require channel binding security (channelBinding=require) can be silently downgraded to a weaker authentication method. An attacker positioned to intercept TLS traffic can force this downgrade by presenting a certificate with an unsupported signature algorithm, causing the driver to drop the man-in-the-middle protection that channel binding provides. The vulnerability stems from incomplete validation: the driver checks only that the server advertises a secure mechanism but fails to reject empty or missing channel-binding data. Version 42.7.12 and later fix this issue.

  • CVE-2026-6092MEDIUM 5.3

    CVE-2026-6092 is a cryptographic implementation flaw in WolfSSL where the library may unexpectedly downgrade from the stronger Encrypt-then-MAC mode to the weaker MAC-then-Encrypt mode, even when configured to enforce Encrypt-then-MAC. This downgrade weakens the integrity guarantees of TLS connections by allowing potential plaintext recovery attacks. An attacker on the network can exploit this without authentication to read sensitive data transmitted over affected connections.

  • CVE-2026-54780LOW 3.7

    CoreWCF, a .NET Core implementation of Windows Communication Foundation, has a flaw in how it validates cryptographic signatures on incoming messages. Specifically, the library checks that the overall signature algorithm meets security standards but fails to validate the digest algorithms used for individual message components. This means an attacker could use a weak algorithm like SHA-1 to sign parts of a message, and CoreWCF would still accept it as valid. The risk is limited—the attacker cannot decrypt messages or cause service outages—but they could potentially tamper with message contents in ways that go undetected. Versions 1.8.1 and 1.9.1 and later close this gap.