api-versioning
Find and attack old/shadow API versions that missed a fix — improper inventory management. Load when the API is versioned (/v1, /v2, /api/2021-01), on "old API", or after mapping the surface. Signals: version in path/header/subdomain, deprecated docs, mobile app using an older version.
v2026.10.14-ee0e0c53 installs+3 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/api-versioningWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package979a56fd…3ca83688
979a56fd83c8…a31a3ca836881 file · 1.3 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-versioning@ee0e0c5
On this page
When it applies
The API exposes multiple versions and a vulnerability fixed in the current version still lives in an older or undocumented one. Old versions rarely get the same auth, validation, or rate-limit hardening.
Why it works
Teams patch the latest version and leave /v1 (and /beta, /internal, dated versions) running
for backward compatibility. Those endpoints often skip a fix, lack a new authz check, or expose
fields later removed — same data, weaker guard.
Method
- Enumerate versions: swap the version in path (
/v1↔/v2↔/v3), header (Accept: application/vnd.api+json;version=1,X-API-Version), or subdomain (api-v1.,legacy.). Fuzz withffuf. - Diff behaviour: take a request that's now blocked/fixed on the current version and replay it
against older ones — missing auth, mass assignment (→
api-mass-assignment), BOLA (→api-bola), verbose fields, or no rate limit. - Mine sources for old versions: mobile apps, JS bundles, wayback, and public API docs often reference deprecated versions still live.
- Re-test every known bug per version — a fix in v2 is often absent in v1.
Gotchas
- A 404 on
/v1root doesn't mean v1 is gone — test specific known endpoints under it. - Header/media-type versioning is easy to miss vs path versioning — enumerate all three.
- Old versions may lack rate limits, enabling brute force the new one blocks.
Verify success
A vulnerability reproducible on an older/undocumented API version that is patched or better-guarded on the current one.
References
OWASP API Security Top 10 (2023) API9; API inventory/versioning guidance.
Files in this version
- SKILL.md2.2 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
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.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 979a56fd | Signed | – |
More from NoorQureshi
All from this publisherMore in APIs, SaaS and identity
See the category- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login