Export limit exceeded: 396005 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 396005 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 396005 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 396005 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (396005 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-93600 | 1 Rustls | 1 Webpki | 2026-09-19 | 2.2 Low |
| rustls-webpki (rustls/webpki) versions 0.101.0 through 0.103.11 and 0.104.0-alpha releases before 0.104.0-alpha.6 ignore X.509 name constraints that apply to URI names, causing such constraints to be accepted rather than enforced. Because name constraints are restrictions on otherwise properly issued certificates, the flaw is only reachable after successful signature verification and requires a misissued certificate to exploit; the library also provides no API for asserting URI names, and URI name constraints are otherwise unimplemented. Versions 0.103.12 and 0.104.0-alpha.6 reject URI name constraints unconditionally. | ||||
| CVE-2026-93601 | 1 Rustls | 1 Webpki | 2026-09-19 | 2.2 Low |
| rustls-webpki (the Rust webpki fork used by rustls) versions >= 0.101.0 and prior to 0.103.12 and 0.104.0-alpha.6 incorrectly accepted permitted-subtree DNS name constraints for certificates asserting a wildcard name. For example, a name constraint of accept.example.com was treated as satisfied by a certificate for *.example.com, which could feasibly assert reject.example.com — a name outside the permitted subtree. Because name constraints are restrictions applied to otherwise properly issued certificates, the issue is only reachable after signature verification succeeds and requires a misissued wildcard certificate to exploit. | ||||
| CVE-2026-93602 | 1 Rustls | 1 Webpki | 2026-09-19 | 4.4 Medium |
| rustls-webpki versions before 0.103.10 and 0.104.0-alpha.5 contain faulty CRL authority-matching logic that compares only the first distributionPoint against each CRL's IssuingDistributionPoint, ignoring additional distributionPoints. Attackers with a compromised trusted issuing authority can present revoked certificates that pass revocation checks under UnknownStatusPolicy::Allow, or cause incorrect errors under the default deny policy. | ||||
| CVE-2026-25684 | 1 Zscaler | 1 Zia File Type Control | 2026-09-19 | 4.4 Medium |
| A file type attribution issue in Zscaler Internet Access File Type Control evaluation rules may allow improper evaluation of File Type Control policies in rare circumstances. | ||||
| CVE-2026-93657 | 1 Hickory-dns | 1 Hickory-resolver | 2026-09-19 | 7.5 High |
| hickory-resolver versions before 0.26.2 fail to propagate bogus DNSSEC proof states through the Resolver::lookup() and Resolver::lookup_ip() APIs, allowing invalid records to be returned as successful results. Attackers controlling the answering zone or positioned on the network path can have forged DNS records accepted as validated, bypassing DNSSEC authentication checks. | ||||
| CVE-2026-93659 | 2 Concretecms-community-store, Nbubna | 2 Community Store, Store | 2026-09-19 | 8.7 High |
| Concrete CMS Community Store before 2.7.8 renders customer-supplied order fields without HTML escaping in checkout and admin views. Unauthenticated attackers can store script payloads in billing name, email, or phone fields that execute in authenticated manager sessions to create rogue accounts or exfiltrate data. | ||||
| CVE-2026-93576 | 2 Io.netty, Redhat | 7 Netty-codec-http, Build Of Apache Camel For Spring Boot, Camel Spring Boot and 4 more | 2026-09-19 | 7.5 High |
| A flaw was found in Netty netty-codec-smtp. The component does not properly validate Carriage Return (CR) and Line Feed (LF) characters in the SMTP command-name field. A remote attacker, if an application routes untrusted input into this field, can embed CR/LF characters to inject arbitrary SMTP commands. This can lead to SMTP command smuggling, allowing for unauthorized email relay or spoofing of sender/recipient addresses. While the impact is significant, the real-world exploitability is considered lower as applications typically do not place user-controlled data in the command-name field. | ||||
| CVE-2026-81943 | 1 Planet Technology Corp | 2 Planet Igs-5225-8p2t4s V1, Planet Igs-5225-8p2t4s V2 | 2026-09-19 | 6.7 Medium |
| PLANET IGS-5225-8P2T4S industrial managed switch V1 and V2 firmware versions before 1.2412b260707 and 2.2412b260519 contain active debug functionality in the embedded software. An attacker with privileged access to the device can enable this debug mode to execute arbitrary code on the underlying operating system and gain root-level access. | ||||
| CVE-2026-81944 | 1 Planet Technology Corp | 2 Planet Igs-5225-8p2t4s V1, Planet Igs-5225-8p2t4s V2 | 2026-09-19 | 7.5 High |
| PLANET IGS-5225-8P2T4S industrial managed switch V1 and V2 firmware versions before 1.2412b260707 and 2.2412b260519 contain a stack-based buffer overflow in the web server. Insufficient bounds checking on data copied into a stack buffer allows a remote authenticated attacker to cause a denial of service or potentially execute arbitrary code on the underlying operating system. | ||||
| CVE-2026-81945 | 1 Planet Technology Corp | 2 Planet Igs-5225-8p2t4s V1, Planet Igs-5225-8p2t4s V2 | 2026-09-19 | 6.6 Medium |
| PLANET IGS-5225-8P2T4S industrial managed switch V1 and V2 firmware versions bfore 1.2412b260707 and 2.2412b260519 contain a stack-based buffer overflow in the web server. Insufficient bounds checking on data copied into a stack buffer allows a remote administrator to cause a denial of service or potentially execute arbitrary code on the underlying operating system. | ||||
| CVE-2026-81946 | 1 Planet Technology Corp | 2 Planet Igs-5225-8p2t4s V1, Planet Igs-5225-8p2t4s V2 | 2026-09-19 | 4.4 Medium |
| PLANET IGS-5225-8P2T4S industrial managed switch V1 and V2 firmware versions before 1.2412b260707 and 2.2412b260519 use MD5-based password hashing, a cryptographic algorithm with known weaknesses. An attacker who obtains the device configuration file can recover the privileged-mode access password. | ||||
| CVE-2026-75031 | 1 Interchange | 1 Interchange | 2026-09-19 | 9.8 Critical |
| In the interchange/interchange project, a critical remote code execution (RCE) vulnerability was found in the “quick question” admin feature. In default installations arbitrary Perl code can be injected and executed server-side by unauthenticated users. The Perl code normally runs within a Safe container which limits the scope of what it can do, unless the non-default AllowGlobal directive is configured for the catalog being accessed.CTOR] | ||||
| CVE-2026-75883 | 1 Ppp Project | 1 Ppp | 2026-09-19 | 6.8 Medium |
| The code in pppd that formats a response to a PEAP Request packet in peap_response() copies an entire TLS record of up to 16384 bytes into the fixed global buffer outpacket_buf without checking the available space and without implementing outgoing PEAP fragmentation. Thus a pppd process connecting to a server which requests PEAP authentication can be induced to corrupt global static data following the outpacket_buf array, most likely causing incorrect behavior or a crash. | ||||
| CVE-2026-86520 | 1 Bransys | 1 Eld | 2026-09-19 | 7.5 High |
| Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read access to real-time data for every active device across a subset of carriers that were connected to the affected MQTT broker. | ||||
| CVE-2026-86689 | 1 Bransys | 1 Eld | 2026-09-19 | 5.9 Medium |
| Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read access to real-time data for every active device across a subset of carriers that were connected to the affected MQTT broker. | ||||
| CVE-2026-77960 | 1 Bransys | 1 Eld | 2026-09-19 | 5.3 Medium |
| Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read access to real-time data for every active device across a subset of carriers that were connected to the affected MQTT broker. | ||||
| CVE-2026-84398 | 1 Carecam | 1 Hmt.cm2507 Firmware | 2026-09-19 | 7.5 High |
| CM2507 IP cameras accept an empty password for a privileged account exposed through its ONVIF management service. An attacker with network access to the affected device could access privileged management functions and obtain device, user, media-profile, and stream configuration information. | ||||
| CVE-2026-54148 | 1 Http4k | 1 Http4k | 2026-09-19 | 8.1 High |
| http4k is a functional toolkit for Kotlin HTTP applications. Prior to 4.51.0.0, 5.42.0.0, and 6.50.0.0, DigestAuthProvider.verify in http4k-security-digest does not compare the uri parameter in an Authorization: Digest response with the actual request URL. An attacker who captures a valid Digest authentication response can replay it against another URL served by the same realm, bypassing the per-request-URI binding and potentially gaining unauthorized read or write access. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0. | ||||
| CVE-2026-84400 | 1 Carecam | 1 Hmt.cm2507 Firmware | 2026-09-19 | 3.1 Low |
| CareCam CM2507 IP cameras contain an insufficiently protected network maintenance mechanism that can activate a remote debugging service. An attacker on the same local network who satisfies certain device state conditions could make the service remotely accessible, increasing the risk of unauthorized administrative access. | ||||
| CVE-2026-54147 | 1 Http4k | 1 Http4k | 2026-09-19 | 6.5 Medium |
| http4k is a functional toolkit for Kotlin HTTP applications. Prior to 4.51.0.0, 5.42.0.0, and 6.50.0.0, DigestAuthProvider.verify in http4k-security-digest ignores its configured algorithm parameter and verifies every Digest response with hardcoded MD5. Deployments configured for SHA-256 therefore receive weaker MD5-based verification, exposing Digest authentication to collision-related attack paths that depend on the hash function's collision resistance. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0. | ||||