CVE-20XX-?
agent?

Just published.

The newest CVEs, straight from CVE.org and NVD.

385 CVEs · updated 2026-11-19 11:08 UTC

Reset all
  1. CVE-2026-122100

    CAI Content Credentials is affected by an Improper Verification of Cryptographic Signature vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page.

    Crypto Library

    5.5 MEDIUM 0.3% exploit odds No fix listed
  2. CVE-2026-113572

    CAI Content Credentials is affected by a Use of a Broken or Risky Cryptographic Algorithm vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.

    Crypto Library

    5.9 MEDIUM 0.5% exploit odds No fix listed
  3. CVE-2026-120808

    An issue exists in MongoDB's macOS TLS client implementation where certificate chain-of-trust validation is bypassed for outbound connections to IPv6-addressed peers. When a MongoDB process using the Apple SecureTransport TLS backend connects to an IPv6 target, the trust evaluation result from SecTrustEvaluate is silently discarded, regardless of whether the peer's certificate is trusted. An on-path party could exploit this by presenting a self-signed certificate containing the target's IPv6 address in the Subject Alternative Name to intercept and modify encrypted inter-node or external service traffic. This issue only affects MongoDB processes running on macOS with the Apple SecureTransport TLS provider.

    Crypto OS & kernel

    9.1 CRITICAL 0.2% exploit odds No fix listed
  4. CVE-2026-125335

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, ed25519.verify() decodes a public key in crypto_sign_open() without rejecting small-order points or their non-canonical encodings. With S = 0 and a small-order R value, an attacker who can choose the public key can produce signatures that verify for many messages, or all messages with the identity key, without a private key. This can defeat proof-of-possession, attribution, non-repudiation, or deduplication checks that rely on a signature being bound to the message. Keys produced by normal Ed25519 key generation are not small-order, so applications that verify only trusted or internally generated public keys are not affected. This issue is fixed in version 1.4.3.

    Crypto Digitalbazaar Forge

    3.7 LOW 0.2% exploit odds Fix listed
  5. CVE-2026-125336

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths. A name-constrained certificate authority with a non-critical extension can therefore issue a leaf certificate with a subjectAltName dNSName or subject commonName outside a permitted subtree or inside an excluded subtree, and node-forge accepts the chain. Exploitation requires a name-constrained CA that chains to a trusted root and either its private key or the ability to obtain an out-of-scope certificate, allowing impersonation of names outside the delegated namespace, including against forge.tls clients. Chains without nameConstraints are not affected, and affected versions safely reject critical nameConstraints as unsupported rather than accepting them. This issue is fixed in version 1.4.3.

    Crypto Digitalbazaar Forge

    7.4 HIGH 0.2% exploit odds Fix listed
  6. CVE-2026-118102

    Use of a broken or risky cryptographic algorithm in SQL Server allows an unauthorized attacker to disclose information over a network.

    Crypto Server Microsoft SQL Server 2017 (GDR)

    5.9 MEDIUM 0.5% exploit odds Fix listed
  7. CVE-2026-119867

    Improper verification of cryptographic signature in Windows Installer allows an unauthorized attacker to bypass a security feature over a network.

    Crypto OS & kernel Microsoft Windows 10 Version 1607

    5.3 MEDIUM 0.4% exploit odds Fix listed
  8. CVE-2026-118737

    Improper verification of cryptographic signature in Windows Remote Procedure Call Runtime allows an unauthorized attacker to execute code over a network.

    Crypto OS & kernel Microsoft Windows 10 Version 1607

    8.1 HIGH 0.7% exploit odds Fix listed
  9. CVE-2026-70003

    Improper verification of cryptographic signature in JDBC Driver for SQL Server allows an unauthorized attacker to bypass a security feature over a network.

    Crypto OS & kernel Microsoft JDBC Driver For SQL Server 13.4

    8.7 HIGH 0.3% exploit odds Fix listed
  10. CVE-2026-102219

    Inadequate encryption strength in Windows Modern Device Management (MDM) allows an unauthorized attacker to execute code over a network.

    Crypto OS & kernel Microsoft Windows 10 Version 1809

    8.1 HIGH 0.4% exploit odds Fix listed
  11. CVE-2026-113763

    Use of a broken or risky cryptographic algorithm in Windows DPAPI (Data Protection Application Programming Interface) allows an authorized attacker to elevate privileges locally.

    Crypto OS & kernel Microsoft Windows 10 Version 1607

    6.3 MEDIUM 0.2% exploit odds Fix listed
  12. CVE-2026-95910

    Improper certificate validation in Windows Hyper-V allows an authorized attacker to bypass a security feature locally.

    Crypto OS & kernel Microsoft Windows 10 Version 1607

    6.7 MEDIUM 0.3% exploit odds Fix listed
  13. CVE-2026-105590

    Improper certificate validation in Windows Active Directory Certificate Services allows an authorized attacker to bypass a security feature over a network.

    Crypto OS & kernel Microsoft Windows Server 2016

    5.3 MEDIUM 0.5% exploit odds Fix listed
  14. CVE-2026-42067

    Improper certificate validation for some Intel(R) TDX Workload Attestation software within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable data manipulation. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

    Crypto

    5.9 MEDIUM 0.1% exploit odds No fix listed
  15. CVE-2026-87758

    The remote EJB client does not verify that the hostname of the server it connects to matches the server's TLS certificate. An attacker able to intercept network traffic between an EJB client and server can impersonate the server and read or modify the traffic, including credentials and invocation data. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

    Crypto Server

    7.4 HIGH 0.1% exploit odds Fix listed
  16. CVE-2026-111259

    The embedded server generates HTTP session identifiers with a non-cryptographic random number generator by default. A remote attacker who observes a session identifier can predict the identifiers issued to other users and hijack their sessions, if the application relies on HTTP sessions for authentication. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

    Crypto Web app

    9.1 CRITICAL 0.3% exploit odds Fix listed
  17. CVE-2026-111260

    The Jakarta Security OpenID Connect authentication mechanism generates the state and nonce values with a non-cryptographic random number generator and insufficient entropy. A remote attacker who predicts these values can forge an authentication callback that logs a victim into the attacker's account, and the replay protection for ID tokens is weakened. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

    Crypto Web app

    9.1 CRITICAL 0.4% exploit odds Fix listed
  18. CVE-2026-87755

    Stateful session bean identifiers are not generated from a cryptographically secure random source. A remote attacker with access to the EJB remote endpoint who holds one valid identifier can derive those of other clients' sessions and invoke methods on their beans, exposing or modifying other users' session state. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

    Crypto Server

    7.5 HIGH 0.4% exploit odds Fix listed
  19. CVE-2026-82509

    V programming language standard library net.http through version 0.5.2 prior to commit 4077484 contains a TLS certificate validation bypass vulnerability that allows on-path attackers to intercept HTTPS traffic by exploiting the default false value of SSLConnectConfig.validate and FetchConfig.validate, which completes TLS handshakes without verifying certificates in both the mbedtls and OpenSSL backends. Attackers can present an expired, self-signed, wrong-hostname, or untrusted-root certificate to successfully complete the handshake via http.get, http.post, or http.fetch, enabling interception or modification of HTTPS traffic unless validate: true is explicitly configured.

    Crypto Library

    9.1 CRITICAL 0.2% exploit odds Fix listed
  20. CVE-2026-4762

    A vulnerability to perform a privilege escalation attack on the server as a non-admin user.

    Crypto Device

    8.8 HIGH 0.1% exploit odds No fix listed
  21. CVE-2026-120017

    SAP NetWeaver AS ABAP and ABAP Platform does not perform sufficient verification of incoming authentication assertions under certain configurations. An unauthenticated attacker could submit specially crafted data to bypass authentication and impersonate arbitrary users, including privileged accounts. Successful exploitation could cause a full system compromise, with the impact potentially extending to connected components and systems beyond the affected system. This results in a high impact on confidentiality, integrity, and availability of the application.

    Crypto

    10.0 CRITICAL 0.3% exploit odds No fix listed
  22. CVE-2026-109799

    The SAP Cloud SDK for Python contains an improper cryptographic signature verification vulnerability (CWE-347) in IASContextProvider, the runtime-context provider registered by default via bootstrap(app).IASContextProvider extracted the app_tid, sap_gtid and user_uuid claims from the IAS JWT in the Authorization header using an unverified decoder and wrote them into the request-scoped RuntimeContext without validating the token signature. A remote caller could submit a self-signed JWT naming a victim tenant/user; the forged identity then propagated to every consumer of the runtime context:OTel span attributes (sap.tenancy.tenant_id, user.id) via RuntimeContextSpanProcessorlog records via IdentityLogFilteraudit events (tenant_id, user_initiator_id) via AuditClienttenant routing via CBCClientThis completes an earlier remediation that fixed the same unverified pattern in StarletteIASTelemetryMiddleware but did not cover IASContextProvider.

    Crypto Library

    7.5 HIGH 0.2% exploit odds Fix listed
  23. CVE-2026-121688

    FrodoBots EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) contains an insecure STM32 firmware update mechanism. The STM32 motor‑controller firmware is fetched over unencrypted HTTP. Integrity is validated only via MD5, with the hash provided in the same unprotected response. No code‑signing mechanism is implemented, allowing firmware to be replaced with potentially malicious code.

    Crypto Device

    9.1 CRITICAL 0.2% exploit odds No fix listed
  24. CVE-2026-112165

    The LaserGest mobile application disables TLS certificate and hostname verification via setServerTrustMode("nocheck"), allowing a man-in-the-middle attacker to intercept or modify network traffic, including credentials and API communications.

    Crypto Device

    6.9 MEDIUM 0.2% exploit odds No fix listed
  25. CVE-2026-19552

    When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.

    Crypto Library

    0.0 NONE 0.3% exploit odds Fix listed
  26. CVE-2026-95779

    An exposure of the appliance’s confidential certificate information  vulnerability exists in HPE Morpheus manager software.

    Crypto

    8.8 HIGH 0.2% exploit odds No fix listed
  27. CVE-2026-78537

    IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 could allow a local attacker to obtain sensitive information due to the use of a weak cryptographic algorithm.

    Crypto

    6.8 MEDIUM 0.1% exploit odds No fix listed
  28. CVE-2026-14375

    IBM Storage Scale 5.2.3.0 through 5.2.3.8, and 6.0.1.0 does not validate or improperly validates TLS certificate validation when communicating with remote cluster GUI interfaces, which could allow an attacker to inject forged JSON responses using man in the middle techniques.

    Crypto Server

    5.9 MEDIUM 0.2% exploit odds No fix listed
  29. CVE-2026-14434

    IBM Turbonomic kubeturbo agent 8.16.0 through 8.21.2 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.

    Crypto

    5.9 MEDIUM 0.1% exploit odds No fix listed
  30. CVE-2026-14435

    IBM Turbonomic kubeturbo agent 8.16.0 through 8.20.3 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.

    Crypto

    5.9 MEDIUM 0.1% exploit odds No fix listed
  31. CVE-2026-105970

    The Thanh Toán Quét Mã QR Code Tự Động WordPress plugin through 2.0.1 does not properly verify the authenticity of incoming bank-transfer payment notifications on a default installation, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid.

    Crypto Web app

    5.3 MEDIUM 0.2% exploit odds No fix listed
  32. CVE-2026-123611

    rustls before 0.23.46 contains a key exchange downgrade vulnerability that allows network attackers to poison the per-server-name key-exchange group record via an unauthenticated ServerHello. Attackers can answer one connection with a ServerHello selecting X25519, causing later ClientHellos to send only classical shares and lose post-quantum confidentiality.

    Crypto Server

    6.3 MEDIUM 0.2% exploit odds Fix listed
  33. CVE-2026-123613

    Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A peer or on-path attacker can pack a plaintext EncryptedExtensions with the ServerHello, which rustls accepts unencrypted.

    Crypto

    6.9 MEDIUM 0.2% exploit odds Fix listed
  34. CVE-2026-123605

    Hickory DNS hickory-proto 0.1 through 0.25.0-alpha.3 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because the validator verifies an RRSIG against the DNSKEY of whatever name appears in its Signer's Name field without checking that this name is the zone containing the RRset. Attackers controlling any secure zone can produce valid signatures over arbitrary records in unrelated zones, which resolvers, recursors, and clients using DnssecDnsHandle accept as authenticated.

    Crypto

    8.7 HIGH 0.2% exploit odds Fix listed
  35. CVE-2026-123596

    Hickory DNS hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw in the validating recursor's NSEC handler that accepts parent-side ancestor-delegation NSEC records as proof of nonexistence for names below the zone cut. An on-path attacker, rogue parent nameserver, or attacker winning a port and TXID race can deliver one forged NXDOMAIN response built from genuinely signed parent NSEC records, causing authenticated denial of existing child-zone names cached for the negative TTL.

    Crypto

    8.7 HIGH 0.2% exploit odds Fix listed
  36. CVE-2026-123599

    Hickory DNS hickory-proto before 0.26.0-beta.1 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because verify_rrsets() ignores DNS class when partitioning RRsets, so non-IN records skip signature verification yet are marked secure when the IN records verify. Attackers able to supply DNS responses can include forged CH or HS class records, including DS records, to authenticate any DNSKEY and forge child zone responses.

    Crypto

    6.3 MEDIUM 0.1% exploit odds Fix listed
  37. CVE-2026-123600

    Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net 0.26.0-alpha.1 before 0.26.2 contain a DNSSEC validation flaw in DnssecDnsHandle that accepts NSEC3-signed NODATA responses for zone-apex queries as secure without an NSEC3 record matching the hashed QNAME. On-path attackers or malicious authoritative servers can replay a validly signed non-apex NSEC3 with the zone's signed SOA to serve an authenticated (AD=1) denial of any apex RRtype for the negative-cache TTL.

    Crypto

    6.3 MEDIUM 0.2% exploit odds Fix listed
  38. CVE-2026-123590

    Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 accept NSEC and NSEC3 records for DNSSEC nonexistence proofs when any other record with the same owner name passes signature validation. Attackers able to supply DNS responses can mix validly signed records with bogus same-name NSEC or NSEC3 records of different types in the authority section to forge nonexistence proofs.

    Crypto

    6.3 MEDIUM 0.2% exploit odds Fix listed
  39. CVE-2026-123591

    Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 fail to verify, per RFC 6840 §4.4, that an NSEC or NSEC3 record denying a DS RRset also proves the delegation's NS record exists. Attackers can reuse child-side NSEC or NSEC3 records to fake an insecure delegation and forge child-zone records.

    Crypto

    8.2 HIGH 0.1% exploit odds Fix listed
  40. CVE-2026-123592

    The hickory-net crate in Hickory DNS 0.26.0-beta.1 before 0.26.2 allows DNSSEC validation bypass because Name's Hash ignores label lengths and ValidationCacheKey compares only that hash. An attacker controlling an unsigned delegation whose name differs from a signed target only in dot positions can prime an Insecure verdict, causing forged answers for the target to skip signature verification instead of returning SERVFAIL.

    Crypto Library

    8.2 HIGH 0.3% exploit odds Fix listed
  41. CVE-2026-123593

    Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto 0.24.0 through 0.26.0-alpha.1 compare DNSKEY public keys against DNSSEC trust anchors without checking the DNSKEY record name, so an RRset made up only of trusted keys is accepted without RRSIG verification. Attackers able to spoof or control name server responses can replace a secure zone's DNSKEY RRset with the root zone's keys, and use a large TTL to keep it cached.

    Crypto Server

    6.3 MEDIUM 0.2% exploit odds Fix listed
  42. CVE-2026-123595

    Hickory DNS hickory-proto 0.25 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw in the validating recursor's NSEC3 handler, which matches the closest encloser by hash alone without checking the type bitmap and so accepts parent-side ancestor-delegation NSEC3 records as proof of nonexistence. An attacker who delivers one response built from genuinely signed parent NSEC3 records can cause NXDOMAIN or NODATA to be cached with AD=1, denying resolution of existing names at and below the zone cut.

    Crypto

    8.7 HIGH 0.2% exploit odds Fix listed
  43. CVE-2026-123579

    DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.

    Crypto

    6.3 MEDIUM 0.2% exploit odds Fix listed
  44. CVE-2026-123581

    Hickory DNS hickory-proto through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw that accepts a response as a positive answer when any valid RRset appears in the answer section, without checking that the RRset is responsive to the query. Attackers can supply signed but unrelated RRsets so that responses lacking matching records are validated as positive answers instead of as no-data responses.

    Crypto

    6.9 MEDIUM 0.1% exploit odds Fix listed
  45. CVE-2026-123538

    OpenAM before 16.1.4 does not verify that a signed SAML 1.x assertion or response was signed by the partner named as its issuer, accepting a signature from any certificate in OpenAM's keystore. An attacker holding such a private key, such as a trusted SAML 1.x partner, can forge assertions claiming another partner's issuer and sign in as that partner's users, including privileged ones.

    Crypto Openidentityplatform Openam

    7.5 HIGH 0.1% exploit odds Fix listed
  46. CVE-2026-19126

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

    Crypto Server IBM Api Connect

    5.9 MEDIUM 0.2% exploit odds Fix listed
  47. CVE-2026-19129

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a network-positioned attacker to intercept backup data due to improper verification of the backup server's identity. The identity of the backup server is not verified when the secure connection for analytics backups is established, which could allow backup data, and credentials if used, to be intercepted.

    Crypto Server IBM Api Connect

    6.8 MEDIUM 0.2% exploit odds Fix listed
  48. CVE-2026-17393

    IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a local attacker to obtain sensitive information due to the use of a cryptographically weak pseudo-random number generator.

    Crypto IBM Api Connect

    5.1 MEDIUM 0.1% exploit odds Fix listed
  49. CVE-2026-17386

    IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a remote attacker to gain full administrative control due to the use of a cryptographically weak pseudo-random number generator.

    Crypto Server IBM Api Connect

    8.1 HIGH 0.5% exploit odds Fix listed
  50. CVE-2026-17379

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to bypass authentication and assign arbitrary roles due to improper verification of cryptographic signatures.

    Crypto IBM Api Connect

    7.4 HIGH 0.3% exploit odds Fix listed

The newest published CVE records from CVE.org and NVD, refreshed every few minutes, with severity, exploit odds and fix status.