— listed CVEs▲
07
Public identifiers
2025 — 2026
§ 00
·
Cybersecurity Researcher · Developer · Builder
I
break,
verify,
patch,
and
build.
I am Ali Firas, a source-code-focused cybersecurity researcher and builder with a strong interest in real-world vulnerability discovery, precise proof-of-concept development, technical reporting, and secure product engineering. My work connects offensive analysis, defensive thinking, and clean execution into one workflow.
focussource audit, PoC, disclosure
methodreproduce → root cause → impact → fix
styleprecise · evidence-driven · patch-aware
moderesearch / reporting / builder
— core focus areas◇
03
Research · PoC · Reporting
one repeatable path
— research mindset§
01
Honest · reproducible · patch-aware
no inflated claims
§ 01 About
A disciplined
engineering process.
Research that reads like engineering: trust boundaries first, reproducible evidence second, honest impact always.
I study systems carefully, identify trust boundaries, reproduce flaws cleanly, and communicate findings maintainers can act on quickly.
My work sits at the intersection of vulnerability research, secure software design, proof-driven reporting, and technical product building. I enjoy reading source code, reasoning about exploitability, and translating findings into clear technical reports with realistic threat models, root cause analysis, impact framing, and remediation paths.
I care about findings that are technically honest and practically useful. That means no inflated claims, no weak assumptions, and no vague impact language. I prefer reproducible evidence, exact code paths, realistic attacker models, and fixes that fit maintainers' codebases.
01 · precision
Root-cause first
Analysis with technical clarity and clean reproduction paths.
02 · execution
Idea to patch
Move from idea to report, patch, pull request, or advisory without losing depth.
§ 02 Core Expertise
Where depth meets clarity.
Security research is strongest when technical depth and communication quality move together. These are the areas that define how I work.
01 / discovery
Vulnerability
Research
I analyze application and library behavior for logic flaws, input validation failures, unsafe assumptions, race conditions, file handling issues, and server-side or client-side impact paths.
02 / validation
Proof-of-Concept
Engineering
I turn suspected issues into clean demonstrations that prove the bug, isolate the attack path, and support accurate severity discussions without overclaiming.
03 / reporting
Technical
Reporting
I build reports around root cause, exploitation conditions, attack surface, affected versions, remediation direction, and publication-ready language.
§ 03 Impact Workflow
A repeatable
path, not hype.
The strongest findings usually come from following a repeatable path instead of chasing hype.
i.
Map the Trust
Boundary
Find where untrusted input crosses into sensitive logic, file operations, rendering, authorization, or state transitions.
→ locate · identify the interface
ii.
Reproduce
Cleanly
Build a minimal but realistic path that demonstrates the flaw with stable evidence and without unnecessary noise.
→ prove · minimal, stable, honest
iii.
Frame the
Real Risk
Describe what the flaw allows, what constraints matter, and which attack scenarios remain realistic in practice.
→ report · impact + remediation
§ 04 CVE Portfolio
Disclosed work.
Linked references.
A curated list of public identifiers associated with disclosed work, including linked references and related tracker entries.
2025 · 63095
DoS via improper input validation in hello-video-codec
2025 · 59717
Type confusion / filter bypass in @digitalocean/do-markdownit
2025 · 59716
Unauthenticated user enumeration in ownCloud Guests registration flow
2025 · 67125
Signed integer overflow in docopt.cpp with downstream distro tracking
2025 · 67124
TOCTOU + symlink race in miniserve upload finalization path
2025 · 13437
zx cleanup path leading to unintended external node_modules deletion
2026 · 25500
Stored XSS in Rack::Directory via javascript:-prefixed filenames
§ 05 Connect
Connect.
Research, collaboration, responsible disclosure, technical networking, and portfolio access.
01 — Contact Channels
Direct channels for research communication, public profiles, and platform presence.
02 — Profile Snapshot
Cybersecurity researcher focused on source code, exploitability analysis, technical reporting, and high-signal disclosure workflows. I like findings that stand up technically, read clearly, and help maintainers fix fast.