Export limit exceeded: 421174 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 421174 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 421174 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (421174 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-123569 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| The devalue package for npm before 5.6.3 can consume excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who manages to get a sparse array created on the server, which mainstream wire formats do not allow, and serialized there can cause a denial of service. | ||||
| CVE-2026-123568 | 1 Svelte | 1 Devalue | 2026-11-08 | 4.4 Medium |
| Sveltejs devalue before 5.6.3 contains a prototype pollution vulnerability that allows attackers to alter object prototypes by supplying untrusted data to uneval. When the generated code is later evaluated, it creates objects with polluted prototypes, producing output data whose shape differs from the original input. | ||||
| CVE-2026-123567 | 1 Svelte | 1 Devalue | 2026-11-08 | 3.7 Low |
| Sveltejs devalue before 5.6.4 contains a prototype injection vulnerability that allows attackers to inject __proto__ own properties into objects returned by devalue.parse and devalue.unflatten. Attackers can supply crafted serialized input that, when downstream code merges results via Object.assign, alters the target object's prototype. | ||||
| CVE-2026-123566 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| Sveltejs devalue before 5.9.3 contains a denial of service vulnerability that allows attackers to cause CPU amplification by supplying sparse arrays to uneval. Attackers who influence sparse values passed to uneval can force synchronous work proportional to the declared array length, blocking the event loop. | ||||
| CVE-2026-123565 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| Sveltejs devalue before 5.9.3 contains a resource exhaustion vulnerability where repeated primitive strings cause quadratic expansion in the uneval function. Attackers can supply a small crafted payload that is parsed and then passed to uneval, producing a very large serialized string that exhausts memory or CPU. | ||||
| CVE-2026-123564 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| Sveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array serialized by an application can exhaust memory in the browser or runtime evaluating the output. | ||||
| CVE-2026-123563 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| Devalue before 5.9.3 contains a validation bypass vulnerability that allows custom ArrayBuffer revivers to skip typed-array allocation checks in the parse function. Attackers can supply very small crafted input processed by a malformed ArrayBuffer reviver to allocate massive ArrayBuffers, causing memory exhaustion and denial of service. | ||||
| CVE-2026-123562 | 1 Svelte | 1 Devalue | 2026-11-08 | 7.5 High |
| devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned promise. An attacker able to influence the timing or failure of serialized asynchronous values can terminate the Node.js process. | ||||
| CVE-2026-123561 | 1 Svelte | 1 Devalue | 2026-11-08 | 3.7 Low |
| devalue before 5.9.3 allows malformed null-prototype object keys to bypass parse's __proto__ rejection through property-key coercion, an incomplete fix for GHSA-mwv9-gp5h-frr4. Attackers can supply crafted payloads that yield objects with a __proto__ own property, which alone does not cause prototype pollution. | ||||
| CVE-2026-123560 | 1 Zfnd | 1 Zebra | 2026-11-08 | 7.5 High |
| Zebra before 7.0.0 contains an incomplete cleanup vulnerability that allows unauthenticated peers to stall initial sync by serving a forged checkpoint block body. Attackers can supply a body with forged authorizing data near the final checkpoint, leaving rejected hashes in the sent-hash set so the node stops requesting blocks until restart. | ||||
| CVE-2026-123559 | 1 Zfnd | 1 Zebra | 2026-11-08 | 7.5 High |
| Zebra before 7.0.0 contains an inefficient algorithmic complexity vulnerability that allows unauthenticated peers to exhaust verification threads by submitting transactions with many transparent inputs. Attackers can relay invalid transactions with tens of thousands of inputs, forcing quadratic ZIP-244 or ZIP-243 digest recomputation that stalls Rayon-backed block verification for minutes. | ||||
| CVE-2026-123558 | 1 Zfnd | 1 Zebra | 2026-11-08 | 7.5 High |
| Zebra zebrad before 7.0.0 contains a denial of service vulnerability that allows a malicious peer to stall checkpoint sync by cancelling the verifier rewind after a failed commit. Attackers can serve a forged block with altered authorizing data plus a restart-triggering block, leaving the verifier rejecting honest blocks until restart. | ||||
| CVE-2026-123556 | 1 Zfnd | 1 Zebra | 2026-11-08 | 5.3 Medium |
| ZcashFoundation Zebra from 4.5.0 before 7.0.0 contains a protection mechanism failure that bans honest peers by scoring mempool lock-time rejections at the ban threshold. Attackers can broadcast transactions locked until the current height right after each block, causing lagging nodes to ban honest relaying peers for 24 hours or until restart. | ||||
| CVE-2026-123554 | 1 Zfnd | 1 Zebra | 2026-11-08 | 7.5 High |
| Zebra zebrad 6.4.0 before 7.0.0 performs quadratic work in the mempool coinbase-maturity check because Transaction::coinbase_spend_restriction() rebuilds the transaction's output list once per spent outpoint. Any connected peer can repeatedly send unsigned transactions with many transparent inputs and outputs, which are rejected without a misbehavior score, to pin verification threads. | ||||
| CVE-2026-123553 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 6.5 Medium |
| OpenAM before 16.1.4 ships built-in identities in the Top Level Realm (demo, anonymous, wsc, wsp, SecurityTokenService and agentAuth) with passwords that are identical on every installation, publicly known, and able to authenticate. Unauthenticated remote attackers can log in as these identities to obtain authenticated sessions, and the agent identities can read the configuration of other agent profiles. | ||||
| CVE-2026-123552 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 6.5 Medium |
| OpenAM before 16.1.4 contains a server-side request forgery vulnerability in certificate CRL checking that fetches CRLs from the distribution point named in a presented certificate without restricting the destination or verifying the downloaded CRL's signature. Attackers holding a trusted-CA-chained certificate can make OpenAM request internal hosts, capture configured CRL update credentials, overwrite stored revocation data to block certificate authentication for that CA, and tie up authentication threads. | ||||
| CVE-2026-123551 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 10 Critical |
| OpenAM from 14.0.0 before 16.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read live session tokens from the notification WebSocket. Attackers can bypass the agent-only check through an unvalidated internal forward on legacy Liberty ID-FF endpoints, collecting iPlanetDirectoryPro tokens to hijack user and administrator sessions. | ||||
| CVE-2026-123550 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 9.8 Critical |
| OpenAM before 16.1.4 contains an authentication bypass vulnerability in its SAML v2.0 service provider that accepts unsigned assertions on the ECP (PAOS) and HTTP-Artifact bindings when WantAssertionsSigned is false. Unauthenticated remote attackers can submit forged assertions to obtain sessions as any mapped user, including administrators, and hijack single sign-on to dependent applications. | ||||
| CVE-2026-123549 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 9.8 Critical |
| OpenAM before 16.1.4 fails to enforce the Valid Creation Attributes list during self-registration, allowing anonymous attackers to set restricted attributes including group membership. Attackers can register through the legacy self-service REST endpoint or User Self-Service flow to join administrative groups and gain full administrative control of OpenAM. | ||||
| CVE-2026-123548 | 1 Openidentityplatform | 1 Openam | 2026-11-08 | 4.7 Medium |
| OpenIdentityPlatform OpenAM before 16.1.4 contains an open redirect because WS-Federation logout, SAML v2.0 logout and name-identifier management, SAML v2.0 identity provider finder, and some authentication pages do not check destination URLs against allowed lists. Attackers can craft OpenAM-domain links that send users to arbitrary external sites for phishing. | ||||