CVE Watch29 de out. de 2026

CVE-2026-33923

A signature verification vulnerability was discovered in the update installation functionality due to inconsistent validation of the update

CVSS

7.2

Alta

EPSS

0.2%

p13

KEV

—

Exploit Today

0-100

Publicado: 29 de out. de 2026 · Última mod.: 29 de out. de 2026 · CWE-347

EPSS · 30d

0.2%EPSS · 30 dias0.2%

2026-10-302026-11-07

Descrição técnica

A signature verification vulnerability was discovered in the update installation functionality due to inconsistent validation of the update bundle contents. An attacker with administrative privileges can remotely supply a crafted update bundle that passes signature verification but runs an unsigned script when the bundle is installed. The script runs with root privileges, allowing the attacker to read or modify sensitive data, change the appliance configuration, or shut down the appliance.

Referências oficiais

security.nozominetworks.comhttps://security.nozominetworks.com/NN-2026:21-01

CVEs relacionados

CVECVSSEPSSKEVRExploitTítuloMod.

CVE-2026-1236058.8 ALT

—

———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.9h CVE-2026-1235904.8 MÉD

—

———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.9h CVE-2026-1235386.6 MÉD

—

———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.9h CVE-2026-173797.4 ALT

27.9%

——8IBM 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.1d CVE-2026-173019.8 CRÍ

38.0%

——11IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow an unauthenticated attacker to bypass authentication due to improper verification of a cryptographic signature.1d CVE-2026-1054596.8 MÉD

11.4%

——3IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow an attacker to gain unauthorized access to an organization due to improper verification of a cryptographic signature. A token is accepted without its signature being fully verified, which could allow an attacker to join an organization without a valid invitation.1d