Node and edge-auth stacks · 6 variants
Docs
Everything Cefense
knows, written down.
The research behind every match — attack classes, control points, and the reasoning Cefense uses to decide a path is reachable. Open to read and search.
No black boxes
Security should never
be a black box.
Every match points back to a page.
When Cefense flags a path, it isn't asking you to trust a score. Behind the finding is the research you can read here.
The attack class, the control point, and why the code was reachable — nothing in the product happens that isn't written down.
The library
So we wrote
all of it down.
Why a valid token isn't a valid session, and where the ownership recheck belongs.
How a replayed device code walks a low-privilege login into an admin route.
The three claims attackers pivot on, and the checks that actually close them.
Reaching the instance metadata endpoint through a permissive redirect.
When a trusted service assumes a role it was never meant to reach.
Buckets and services that read as private but resolve as reachable.
A dependency changes hands, then changes behavior in your build.
Where untrusted code executes during image assembly, and how to gate it.
How an internal name resolves to a public package under the wrong registry.
An agent inherits more than it should when tool scopes aren't isolated.
Model output that steers a tool into an internal request.
Proving the image you scanned is the image that runs.
A restored cache layer smuggles a change past review.
Per-object checks that quietly rot as roles accumulate.
Tracing sensitive fields from store to response, one call at a time.
Finding every place a quantum-vulnerable primitive is still in use.
Certificates, protocols, and libraries that outlive the migration plan.
The reachability model behind every match, in plain language.
Living intelligence
The same signal the
product runs on.
Every entry below is a reconstructed attack primitive — its source, when it was observed, and the semantic variants available for replay.
Six primitives, continuously normalized.
Reconstructed from the source layer, deduplicated, and ranked for relevance before anything reaches you.
Three frameworks · replay available · 4 variants
Two dependencies away · 9 variants
Agentic runtimes and tool routers · 3 variants
OAuth and SSO middleware · 5 variants
CI runners and image promotion · 7 variants
The source layer
Two hundred feeds.
One useful signal.
Cefense does not turn 254 feeds into 254 inboxes. It reconstructs attacker behavior, groups duplicates, and surfaces a primitive only when it changes your risk.
01CISA Advisories
02NIST NVD
03CVE.org
04MITRE ATT&CK
05FIRST EPSS
06BleepingComputer
07The Hacker News
08Krebs on Security
09Dark Reading
10SecurityWeek
11The Record
12PortSwigger Daily Swig
13Google Project Zero
14Unit 42
15The DFIR Report
16Mandiant
17Microsoft Security
18Google Security Blog
19Cisco Talos
20CrowdStrike
21SentinelOne Labs
22Elastic Security Labs
23VirusTotal
24AlienVault OTX
25GreyNoise
26Shodan
27Censys
28URLhaus
29ThreatFox
30Malpedia
31Exploit DB
32Zero Day Initiative
33Packet Storm
34Hybrid Analysis
35ANY.RUN
36Joe Sandbox
37AbuseIPDB
38Spamhaus
39Cloudflare Radar
40Shadowserver
+ more research, malware, infrastructure, cloud, identity, OT, and OSINT sources
The point of it all
Coverage is table stakes.
Reduction is the product.
Reachability, in plain language.
The single idea the whole product rests on — how a live attack becomes a line in your code.
Written for anyone who needs to understand a finding, not only the person who wrote the code it lives in.
Learn one attack class, end to end.
Session boundaries, device-code flows, and JWT confusion.
3 articlesMetadata SSRF, IAM role chaining, and quiet public exposure.
3 articlesOwnership transfer, postinstall scripts, and dependency confusion.
3 articlesDelegated tool permissions and prompt-routed requests.
2 articlesAlways current