Export limit exceeded: 10054 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (10054 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-3360 | 2026-09-02 | 3.3 Low | ||
| The Weaver Show Posts WordPress plugin before 1.8.1 unserialises the content of an imported file, which could lead to PHP object injections issues when a high privilege user import a malicious file and a suitable gadget chain is present on the blog. | ||||
| CVE-2026-16732 | 1 Fastify | 1 Fastify | 2026-09-02 | 6.1 Medium |
| fastify is a fast and low overhead web framework for Node.js. Impact: the fix for CVE-2026-3635 added a guard on the forwarded-header reads used to derive the request host, protocol, hostname, ip, and ips values, checking the connecting address. That guard closes the IP, CIDR, and custom-function forms of trustProxy correctly, because those forms compile to predicates that inspect the connecting address. The hop-count form, where trustProxy is set to a number, compiles to a predicate that structurally ignores the address, so the guard is always satisfied for any hop count of one or more. Applications configured with a numeric trustProxy value, such as trustProxy set to 1 for a single reverse proxy, remain vulnerable: an attacker who can reach the Fastify origin directly, bypassing the front-facing proxy, can spoof the forwarded request fields exactly as in the unpatched version. The impact class matches the parent CVE-2026-3635, including host injection in generated URLs, HTTPS-enforcement bypass, secure-cookie and CSRF-origin bypass, and host-based routing and cache poisoning. Affected versions are fastify from 5.8.3 up to but not including 5.12.1. Patches: patched in fastify 5.12.1, where the numeric form of trustProxy is disabled at runtime and removed from the TypeScript type union. Workarounds: migrate to an IP, CIDR, or custom-function trustProxy value that validates the connecting address, and ensure the Fastify origin is only reachable through the trusted proxy chain. | ||||
| CVE-2026-61753 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-19116 | 2026-09-02 | 8.8 High | ||
| The User Frontend WordPress plugin before 4.3.11 does not prevent user-supplied field values from being deserialized when a submitted post is reopened in its frontend editing form, allowing authenticated users with subscriber-level access and above to perform PHP Object Injection, which may lead to remote code execution when a suitable gadget chain is present on the site. | ||||
| CVE-2026-81283 | 2 Wedevs, Wordpress | 2 Wp User Frontend, Wordpress | 2026-09-02 | 8.8 High |
| Subscriber PHP Object Injection in WP User Frontend <= 4.3.10 versions. | ||||
| CVE-2026-61760 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61761 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61762 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61763 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61764 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61765 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61766 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61767 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61768 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61769 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61770 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61771 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61772 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61773 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61774 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||