proposal-symbol-proto

Abschwächung von Prototype Pollution / Symbol.proto Autoren : Santiago Díaz Google Befürworter : Shu-yu Guo Google Stufe : 1 Inhaltsverzeichnis Problembeschreibung Spukhafte Fernwirkung Probleme mit freeze, seal und preventExtensions Der Override-Fehler Grobe Granularität Einfrierpunkte...

seal-security-nuget-demo-net7

Demo Browser + CLI NuGet/C — Edizione .NET 7 Perché un fork .NET 7? Questo è un fork reindirizzato del fork canonico seal-security-nuget-demo che ha come target net9.0. La storia dello sfruttamento, i controller e l'elenco dei pacchetti sigillati sono identici — cambia solo ilTargetFramework...

Python-Example

Seal Security — Esempio Python pip Un'applicazione Flask minima e intenzionalmente vulnerabile utilizzata per dimostrare, end‑to‑end, come Seal Security ripara una CVE nota sostituendo una dipendenza vulnerabile con una versione sigillata backport, drop‑in — senza alcuna modifica ai requisiti...

JavaScript-Example

Seal Security — Exemplo JavaScript npm Uma aplicação Node.js/Express mínima e intencionalmente vulnerável usada para demonstrar, de ponta a ponta, como a Seal Security corrige um CVE conhecido substituindo uma dependência vulnerável por uma versão selada backport, drop-in — sem nenhuma alteração...

Java-Example

Seal Security — Esempio Java Maven Un'applicazione Spring Boot minima e volutamente vulnerabile, usata per dimostrare, end-to-end, come Seal Security ripara una CVE nota sostituendo una dipendenza vulnerabile con una versione sealed backport, drop-in — senza alcuna modifica alle coordinate...

Seal

Seal Peer-to-Peer-Chat mit Ende-zu-Ende-Verschlüsselung. Kein Posteingang. Kein Konto, das wiederhergestellt werden müsste. Niemand hört mit — nicht einmal wir. github.com/Emn4tor/Seal !GitHub-Issueshttps://img.shields.io/github/issues/Emn4tor/Seal?style=flat-square&color=c9a15c&labelColor=0e11...

CVE-2026-63952

A flaw was found in the Linux kernel's memfd component. When the SEALEXEC flag is used to create a memory file descriptor, the SEALWRITE flag is implicitly applied to prevent writing to executable memory. However, this implicit write protection is applied after checks that should deny writable...

SUSE CVE-2026-63952

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

Linux Distros Unpatched Vulnerability : CVE-2026-63952

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check tha...

CVE-2026-63952

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63952

CVE-2026-63952 affects the Linux kernel: when SEAL_EXEC is added, SEAL_WRITE is implied to enforce W^X, but the implied seal is applied after the write-mapping check. This allows a memfd to be modified via writable mappings despite being marked as write-sealed. The fix adds the implied seals befo...

EUVD-2026-45725

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63952 memfd: deny writeable mappings when implying SEAL_WRITE

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63952

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

CVE-2026-63952 memfd: deny writeable mappings when implying SEAL_WRITE

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...

PT-2026-61269

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the memfd component where the SEAL WRITE seal is implied when SEAL EXEC is added to enforce W^X Write XOR Execute, a security policy ensuring memory is either writable...

Exploit for Improper Input Validation in Pyyaml

Seal Security — Python pip Example A minimal, intentionally...

Unchecked Return Value

Overview Affected versions of this package are vulnerable to Unchecked Return Value due to improper handling of the return value from the verifyintoto function. An attacker can cause the verification process to incorrectly indicate success for DSSE bundles with mismatched in-toto subject digests ...

EUVD-2026-10199

Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows. bin2hex, encrypt, aes256gcmencryptafternm and seal functions do not check that output size will be less than SIZEMAX, which could lead to integer wraparound causing an undersized output buffer. Encountering this...

CVE-2026-30909

Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows. bin2hex, encrypt, aes256gcmencryptafternm and seal functions do not check that output size will be less than SIZEMAX, which could lead to integer wraparound causing an undersized output buffer. Encountering this...