Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-cache-deceptionWeb and bug bounty

web-cache-deception

⁨Trick a CDN/cache into storing a victim's authenticated response at a public URL, then read it. Load on "web cache deception", when a CDN/cache sits in front of an app that serves per-user content, or to test whether private pages can be cached. Signals: `X-Cache`/`CF-Cache-Status` headers, caching ⁩

v2026.10.14-ee0e0c55 installs+5 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-cache-deception

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
V+kJw82PgJ…pUnwDnDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package56470805…9adc140b
564708054e06…8f2b9adc140b1 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-cache-deception@ee0e0c5

When it applies

A caching layer (CDN, reverse proxy) fronts an app that returns per-user content, and the cache decides what to store by URL pattern/extension. If you can make an authenticated response look cacheable, the cache stores it — and anyone can then fetch that victim's data.

Why it works

The cache and the origin disagree about the URL. The cache sees /account.css and thinks "static, cache it"; the origin ignores the .css suffix (or a delimiter) and serves the dynamic /account page. The victim's private response gets stored under a public key you can request.

Method

  1. Confirm the mismatch: request an authenticated page with a static suffix — /account/foo.css, /account%0a.css, /account;foo.js, /account%2ffoo.css. If the origin still returns the account page (not 404), the origin is ignoring the suffix.
  2. Confirm caching: repeat and watch X-Cache/CF-Cache-Status flip to HIT, or a Age header appear. A cached, authenticated response is the vulnerability.
  3. Prove cross-user impact: as the victim, visit the crafted URL once (or have them); then as an unauthenticated attacker request the same URL and receive the victim's private data.
  4. Explore delimiters/normalisation: caches and origins normalise ;, %2f, //, .., trailing dots differently — Param Miner's rules or manual fuzzing find the pair that splits them.
  5. Report with least data: prove one private field leaked; don't hoard victim data.

Gotchas

  • This is not cache poisoning: deception caches a victim's real response; poisoning injects a malicious response via unkeyed input. Different bug, different report (web-cache-poisoning).
  • Needs a genuinely cacheable-looking key and an origin that ignores it — confirm both.
  • Some CDNs cache by content-type, not extension — test path-based tricks too.

Verify success

An unauthenticated request retrieves another user's authenticated content from the cache (HIT/Age present), reproducibly.

References

Omer Gil "Web Cache Deception"; PortSwigger web cache deception labs; CDN caching-rule docs.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c556470805Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login