Overview
- protobufjs
- protobuf.js
Description
Statistics
- 1 Post
Fediverse
🚨 CRITICAL: CVE-2026-41242 in protobuf.js (<7.5.5, 8.0.0-experimental <8.0.1) allows code injection via "type" fields — remote code execution possible. Upgrade to 7.5.5 or 8.0.1+ now! https://radar.offseq.com/threat/cve-2026-41242-cwe-94-improper-control-of-generati-3ca40985 #OffSeq #infosec #protobuff #CVE202641242
Overview
Description
Statistics
- 1 Post
Bluesky
Overview
Description
Statistics
- 1 Post
Fediverse
🚩 SSRF alert: CVE-2026-6573 in PHPEMS 11.0 (MEDIUM, CVSS 5.3) affects /app/exam/controller/exams.master.php via uploadfile argument. Exploit is public — review exposure! https://radar.offseq.com/threat/cve-2026-6573-server-side-request-forgery-in-phpem-e98897b9 #OffSeq #PHPEMS #SSRF #Vuln
Overview
Description
Statistics
- 1 Post
- 7 Interactions
Overview
Description
Statistics
- 1 Post
- 7 Interactions
Overview
Description
Statistics
- 1 Post
Fediverse
Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).
Result: CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). :neocat_glare: #CVE #GCVE
Overview
Description
Statistics
- 1 Post
Fediverse
Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).
Result: CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). :neocat_glare: #CVE #GCVE
Overview
- Microsoft
- Windows 10 Version 1607
Description
Statistics
- 1 Post