Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
security-research — Vulnerability research write-ups — CVE-2026-12478 (libsoup), Apple WebKit, Google VRP | Kitploit
Tools/GitHubGitHub/popy21/security-research
Vulnerability AnalysisPapers & ResearchLearning & EducationCurated Resources
GitHubpopy21/security-research

security-research

Vulnerability research write-ups — CVE-2026-12478 (libsoup), Apple WebKit, Google VRP

View Repository
223 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Security Research

Vulnerability research write-ups. Every entry here corresponds to a fixed, publicly tracked issue — no theoretical findings.

Adel Bouachraoui — hydrasecurity.fr/v10/ · LinkedIn · YesWeHack

Published

Write-upTargetClassID
When a security patch guards the wrong branchGNOME libsoupOut-of-bounds read (CWE-125)CVE-2026-12478

Pending disclosure

Further write-ups are held until the corresponding issue is fixed and disclosure is cleared through the relevant program.

Also credited

  • CVE-2026-28962 — Apple WebKit. Malicious web content leading to sensitive-information disclosure. Fixed in Safari 26.5, macOS, iOS/iPadOS and visionOS. (Apple advisory)

Approach

Source-driven auditing over blind fuzzing. Two things I look for in particular:

  1. Incomplete fixes. A patch is written under time pressure by someone who has already decided what the bug is. That framing is where the second bug lives.
  2. Guards placed inside conditionals. A bounds check is only as good as the set of paths that reach it. Protocol parsers with distinct handling per direction, per opcode or per frame type are structurally prone to this.

Nothing is a finding until an exploit oracle fires. Severity is reported honestly, including when preconditions make a bug hard to reach.

Download Tool