5 reasons to strive for better disclosure processes
Summary: Trail of Bits published five previously undisclosed vulnerabilities it reported over the past year, including unsafe Rust code in the borsh-rs serialization library that went unfixed for two years, DoS bugs in four Ethereum API-parsing libraries, a GCM authentication-tag weakness in expo-secure-store, a memory-allocation crash in num-bigint, and a plaintext encryption key logged by react-native-mmkv. The post attributes the friction to missing coordinated disclosure processes: only one of the four Ethereum projects had GitHub private reporting enabled, Expo never followed up after its initial response and fixed the bug one week after a public-disclosure reminder, and num-bigint users were never notified through an advisory or CVE.
Bottom line: In the Ethereum library case, the reporter had to dig out maintainer emails by appending .patch to GitHub commit URLs, and the post notes that coordinating across vendors grows the reporting burden exponentially rather than linearly - so the cost of a missing security policy lands on whoever finds the bug, and on every user who stays uninformed while it goes unfixed.
Read the original at Trail of Bits Blog ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026