PULSE
FEED
ransommetaencryptor reclama a Christie Digital Systems · US · Technologyransommetaencryptor reclama a Daeah E&C · KR · Manufacturingransommetaencryptor reclama a DAEWON Chemical · KR · Manufacturingransommetaencryptor reclama a Wooshin Systems · KR · Technologyransommetaencryptor reclama a Proterial America, Ltd. · US · Manufacturingransommetaencryptor reclama a Hyundai E&C · KR · Manufacturingransommetaencryptor reclama a Pekin Insurance · US · Financial Servicesransomn0n reclama a Staples, Inc. / SBD Inc. · US · Retail & E-Commerceransomn0n reclama a Lampenwelt GmbH · DE · Retail & E-Commerceransomn0n reclama a Infutor Data Solutions · US · Technologyransomn0n reclama a Higginbotham · US · Professional Servicesransomrhysida reclama a Treuhand & Immobilien Abt AG · CH · Financial Servicesransomwhitearmor reclama a maersk · DK · Transportationransomqilin reclama a Acondistec · DE · Manufacturingransommetaencryptor reclama a Christie Digital Systems · US · Technologyransommetaencryptor reclama a Daeah E&C · KR · Manufacturingransommetaencryptor reclama a DAEWON Chemical · KR · Manufacturingransommetaencryptor reclama a Wooshin Systems · KR · Technologyransommetaencryptor reclama a Proterial America, Ltd. · US · Manufacturingransommetaencryptor reclama a Hyundai E&C · KR · Manufacturingransommetaencryptor reclama a Pekin Insurance · US · Financial Servicesransomn0n reclama a Staples, Inc. / SBD Inc. · US · Retail & E-Commerceransomn0n reclama a Lampenwelt GmbH · DE · Retail & E-Commerceransomn0n reclama a Infutor Data Solutions · US · Technologyransomn0n reclama a Higginbotham · US · Professional Servicesransomrhysida reclama a Treuhand & Immobilien Abt AG · CH · Financial Servicesransomwhitearmor reclama a maersk · DK · Transportationransomqilin reclama a Acondistec · DE · Manufacturing
← All CVEs
CVE WatchNov 7, 2026

CVE-2026-123776

RRD::CGI::Image versions through 0.01 for Perl pass CGI query parameters containting "tz" to tzset(), , so a FIFO or device path blocks the

CVSS

—

No CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 7, 2026 · Last modified: Nov 7, 2026 · CWE-1287

EPSS · 30d

Not enough EPSS history yet.

Technical description

RRD::CGI::Image versions through 0.01 for Perl pass CGI query parameters containting "tz" to tzset(), , so a FIFO or device path blocks the CGI process. The normalize_params method sends any query key matching /tz/i to tz(), which sets $ENV{TZ} to that value, with no validation. It then calls tzset(). glibc treats a TZ value starting with / or : as a file path and opens it, so a value naming a FIFO or a blocking device stalls the process inside tzset().

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1109859.1 CRI
7.2%
——2A Kafka broker using SASL/OAUTHBEARER with the default validator (sasl.oauthbearer.jwt.validator.class=DefaultJwtValidator) selects its implementation from configuration. When sasl.oauthbearer.jwks.endpoint.url is set, the validator verifies the JWT signature. When that URL is unset (the default) and no verification key resolver is supplied, DefaultJwtValidator silently falls back to ClientJwtValidator, which does not verify the JWT signature, algorithm, or issuer - and the broker starts with no warning or error. This is the residual of CVE-2026-33557, whose fix restored signature verification only on the path where the JWKS endpoint URL is set. Impact: A broker in this state accepts any structurally valid JWT, including "alg":"none" tokens. An unauthenticated remote attacker who can reach the listener can forge a token asserting any principal - including configured superusers - and gain full access to the cluster. Only brokers that enable SASL/OAUTHBEARER validation without a JWKS endpoint URL (and without a custom verification key resolver) are affected; brokers that set the URL verify signatures and are not affected. Unlike CVE-2026-110952 (issuer/audience not enforced by default), here no signature is verified at all. Mitigation (all affected versions, no upgrade required): Set sasl.oauthbearer.jwks.endpoint.url for every listener/mechanism that uses OAuthBearerValidatorCallbackHandler, or configure a signature-verifying sasl.oauthbearer.jwt.validator.class. Resolution: From Apache Kafka 4.2.2, 4.3.1, and 4.4.0: a broker that would fall back to the non-verifying ClientJwtValidator fails to start with a ConfigException instead of running without signature verification (secure by default).2d
CVE-2026-904585.4 MED
20.3%
——6OpenStack Ironic before 39.0.1 allows DELETE and GET via vendor_passthru, e.g., to delete accounts from the BMC's Redfish service.9d
CVE-2026-1153834.8 MED
8.0%
——2Wasmtime 47.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contains an improper validation vulnerability that accepts components whose core modules import WebAssembly tags with a subtype of the original type. Malicious guests can mis-type exception object payloads to corrupt the GC heap, causing Wasmtime to panic when the exceptions proposal is enabled.3d
CVE-2026-114509—
79.1%
——24Laravel is a web application framework. Prior to 12.68.0 and 13.29.0, TokenGuard configured as a standard token-based API guard does not reject a crafted non-string credential. Under affected MySQL or MariaDB configurations, the authentication lookup can match an unintended existing user, allowing an unauthenticated attacker to bypass authentication and take over an account on routes protected by TokenGuard. This issue is fixed in versions 12.68.0 and 13.29.0.10d
CVE-2026-1108577.5 HIG
36.2%
——11GitPython before 3.2.0 contains a remote code execution vulnerability that allows attackers to run commands because Git.ls_remote forwards URLs without check_unsafe_protocols validation. Attackers can supply ext:: remote-helper URLs to execute commands when git permits the ext transport, while merge_base and IndexFile.move also accept unguarded option injection.23d
CVE-2026-978017.5 HIG
54.6%
——16Improper validation of specified type of input in .NET Framework allows an unauthorized attacker to perform tampering over a network.25d