Total
398899 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-10686 | 1 Zephyrproject | 1 Zephyr | 2026-08-07 | N/A | 5.8 MEDIUM |
| Zephyr's IPv6 forwarding path re-sent routed unicast packets without ever decrementing the IPv6 hop limit. Both routing branches of ipv6_route_packet() (subsys/net/ip) were affected: the explicit-route path (net_route_packet()) and the on-link cross-interface path (net_route_packet_if()). Each set the packet forwarding flag and called net_send_data() with the hop limit untouched and no expiry check. Per RFC 8200 the hop-limit decrement is the mechanism that bounds packet lifetime and terminates routing loops; without it, a device acting as an IPv6 router relays looping packets indefinitely. An on-path attacker who can induce or exploit a transient L3 loop turns it into a permanent forwarding storm, causing CPU/bandwidth resource exhaustion (availability DoS) on the forwarder and adjacent links; path-discovery and loop diagnostics that rely on hop-limit expiry are also defeated. Affected configurations. In every affected release the forwarding path is reached via CONFIG_NET_ROUTE (enabled by default when CONFIG_NET_IPV6_NBR_CACHE is set), together with CONFIG_NET_ROUTING for cross-interface routing. Note that CONFIG_NET_IPV6_FORWARDING and CONFIG_NET_IPV4_FORWARDING — which appear in the fix and in this advisory's evidence notes — were introduced after v4.4.0, when the routing options were split and renamed; they do not exist in any affected release. When auditing a v4.4.1-or-earlier configuration, look for CONFIG_NET_ROUTE and CONFIG_NET_ROUTING. IPv4 is not affected in any release. The IPv4 forwarding path (net_route_ipv4_packet() in route_ipv4.c) was added after v4.4.0 and has never shipped in a release. Its TTL decrement and IPv4 header-checksum recomputation landed on main as part of the same fix, so the evidence notes below discuss it, but no released version is reachable by way of IPv4. Affected releases are v1.8.0 through v4.4.1: v1.8.0 introduced net_route_packet() and v2.2.0 added net_route_packet_if(), and neither decremented the hop limit. v4.3.1 carries the explicit-route fix but not the on-link one, so it is affected as well. Fixed on main by 7d8f1afa7345 (explicit-route path) and 589eadc74efa (on-link path). | |||||
| CVE-2026-9044 | 1 Tp-link | 2 Archer Axe75, Archer Axe75 Firmware | 2026-08-07 | N/A | 8.0 HIGH |
| An OS command injection vulnerability exists in the VPN module of TP-Link AXE75 V1 routers. This vulnerability allows an adjacent, authenticated attacker to execute arbitrary commands on the device by importing a specially crafted VPN client configuration file. The issue arises from improper filtering of special characters. Successful exploitation of this vulnerability may enable an attacker to gain full control of the affected device, potentially compromising configuration integrity, network security, and service availability. | |||||
| CVE-2026-18536 | 1 Rrwo | 1 Data\ | 2026-08-07 | N/A | 7.5 HIGH |
| Data::Entropy versions before 0.010 for Perl read remote entropy sources over plain HTTP. The Data::Entropy::RawSource::RandomOrg and Data::Entropy::RawSource::RandomnumbersInfo remote sources are accessed over plain HTTP. The Data::Entropy::RawSource::RandomOrg integrity check trivially matches any non-empty byte string. Any on-path attacker, such as open WiFi, a compromised ISP, captive portal, or a hostile egress proxy substitutes the response and thereby chooses the bytes returned by rand_bits and rand_int for every application that selected one of these sources via with_entropy_source. The _checkbuf method response is equally attacker-controlled, so the retry/sleep behaviour is steerable too. | |||||
| CVE-2026-62873 | 1 Microsoft | 1 Windows Admin Center | 2026-08-07 | N/A | 9.8 CRITICAL |
| Improper verification of cryptographic signature in Microsoft 365 Admin Center allows an unauthorized attacker to elevate privileges over a network. | |||||
| CVE-2026-62896 | 1 Microsoft | 1 Teams | 2026-08-07 | N/A | 9.6 CRITICAL |
| Improper authentication in Microsoft Teams allows an authorized attacker to elevate privileges over a network. | |||||
| CVE-2026-58275 | 1 Microsoft | 1 Azure Dns | 2026-08-07 | N/A | 10.0 CRITICAL |
| Missing authorization in Azure DNS allows an unauthorized attacker to elevate privileges over a network. | |||||
| CVE-2026-15080 | 1 Lingotek | 1 Ray Enterprise Translation | 2026-08-07 | N/A | 4.3 MEDIUM |
| Cross-Site Request Forgery (CSRF) vulnerability in Drupal Ray Enterprise Translation allows Cross Site Request Forgery. This issue affects Ray Enterprise Translation versions: from 0.0.0 to 4.0.4, from 4.1.0 to 4.1.4, from 11.0.0 to 11.0.4. | |||||
| CVE-2026-50515 | 1 Microsoft | 1 Azure Service Bus | 2026-08-07 | N/A | 9.9 CRITICAL |
| Deserialization of untrusted data in Azure Service Bus allows an authorized attacker to execute code over a network. | |||||
| CVE-2026-18217 | 1 Redhat | 1 Build Of Keycloak | 2026-08-07 | N/A | 3.4 LOW |
| A flaw was found in the SAML protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs when Keycloak handles SAML authentication requests using the HTTP-Redirect binding. If a client is configured with a wildcard redirect URL, an attacker can craft a request that includes malicious parameters. When a user authenticates, Keycloak appends its legitimate response to the attacker's parameters. This can cause some service providers to process the attacker's data instead of the real login information, potentially leading to a user being logged into the wrong account. | |||||
| CVE-2026-62830 | 1 Microsoft | 1 Azure Sre Agent | 2026-08-07 | N/A | 9.9 CRITICAL |
| Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network. | |||||
| CVE-2026-63508 | 1 Microsoft | 1 Planetary Computer | 2026-08-07 | N/A | 10.0 CRITICAL |
| Missing authentication for critical function in Microsoft Planetary Computer Pro allows an unauthorized attacker to elevate privileges over a network. | |||||
| CVE-2026-70332 | 1 Microsoft | 1 Sharepoint Online | 2026-08-07 | N/A | 9.6 CRITICAL |
| Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network. | |||||
| CVE-2026-17347 | 1 Pgadmin | 1 Pgadmin 4 | 2026-08-07 | N/A | 7.5 HIGH |
| The MASTER_PASSWORD_HOOK setting, introduced in pgAdmin 4 7.2, lets an administrator configure an external command that returns a per-user encryption key, with %u in the configured string replaced by the current user's name. The previous implementation substituted the username directly into the command string and executed the result with subprocess.Popen(..., shell=True). Because the username can originate from an external authentication source (OAuth/OIDC claims, Kerberos, webserver auth) rather than a value pgAdmin fully controls, a username containing shell metacharacters (';', '$()', backticks, pipes, '&&', newlines) allowed an authenticated user to execute arbitrary commands as the pgAdmin service account in any deployment where the configured hook string uses %u. Fix tokenises the trusted, administrator-configured hook string into an argument vector first (using shlex in POSIX-quoting mode, with backslash-escaping disabled so Windows-style paths are not mis-parsed), substitutes the untrusted username into the individual argv elements, and executes with shell=False. The username is therefore always confined to a single argv element; any shell metacharacters it contains are inert. Administrators whose MASTER_PASSWORD_HOOK previously relied on shell features (pipes, redirection, environment-variable expansion, globbing) within the hook string itself must move that logic into the invoked script, since it is no longer interpreted by a shell. This issue affects pgAdmin 4: from 7.2 before 9.17. | |||||
| CVE-2026-47617 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 7.5 HIGH |
| NVIDIA Dynamo for Linux contains a vulnerability in the multimodal media fetcher where an attacker may cause server-side request forgery via DNS rebinding. A successful exploit of this vulnerability might lead to information disclosure. | |||||
| CVE-2026-47618 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 7.5 HIGH |
| NVIDIA Dynamo for Linux contains a vulnerability in the Rust multimodal media fetcher where an attacker could cause server-side request forgery. A successful exploit of this vulnerability might lead to information disclosure. | |||||
| CVE-2026-47619 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 6.6 MEDIUM |
| NVIDIA Dynamo for Linux examples and recipes contain a vulnerability where an attacker could cause a system failure. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure. | |||||
| CVE-2026-47620 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 6.5 MEDIUM |
| NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to data tampering and denial of service. | |||||
| CVE-2026-47621 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 6.5 MEDIUM |
| NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to denial of service and data tampering. | |||||
| CVE-2026-47622 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 5.3 MEDIUM |
| NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause the generation of error messages that contain sensitive information. A successful exploit of this vulnerability might lead to information disclosure. | |||||
| CVE-2026-47623 | 2 Linux, Nvidia | 2 Linux Kernel, Dynamo | 2026-08-07 | N/A | 8.2 HIGH |
| NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to denial of service and data tampering. | |||||