RFC 9839: Defining Safer Unicode Character Subsets for Protocols and Data Structures
Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain Unicode characters encoded in UTF-8. There’s another question, though: “Which Unicode…
Read the full articleYou might also wanna read
RFC 9999: Remote ATtestation procedureS (RATS) Conceptual Message Wrapper (CMW)
The conceptual messages introduced by the Remote ATtestation procedureS (RATS) architecture (RFC 9334) are protocol-agnostic data units that
RFC 9943: A Universal Architecture for Trustworthy and Transparent Digital Supply Chains
Traceability in supply chains is a growing security concern. While Verifiable Data Structures (VDSs) have addressed specific issues, such as
RFC 9943: A Universal Architecture for Trustworthy and Transparent Digital Supply Chains
Traceability in supply chains is a growing security concern. While Verifiable Data Structures (VDSs) have addressed specific issues, such as
CVE-2026-52761: CWE-467: Use of sizeof() on a Pointer Type in owasp-modsecurity ModSecurity
A vulnerability in ModSecurity versions 3.0.0 through 3.0.15 causes the t:utf8toUnicode transformation to produce incorrect output on i386 a
RFC 9933: Carrying SR-Algorithm in Path Computation Element Communication Protocol (PCEP)
This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) to enhance support for Segment Routing (SR)
CVE-2026-46341: CWE-20: Improper Input Validation in apify apify-mcp-server
CVE-2026-46341 is a medium severity vulnerability in the apify-mcp-server prior to version 0.9.21. It involves improper input validation in
CVE-2026-51536: n/a
CVE-2026-51536 is a vulnerability in OpENer 2.3.0 where inconsistent typing of a length parameter during parsing of CIP network packets lead

Comments
Sign in to join the conversation.
No comments yet. Be the first.