API token guessing via unapplied rate limiting
Published Mar 26, 2026 · Updated Mar 26, 2026
Insufficient rate limiting in PinchTab 0.7.7 through 0.8.4 allows remote attackers to guess weak API tokens via repeated HTTP requests. The production handler chain omits RateLimitMiddleware through 0.8.3; in 0.8.4, the health route remains exempt, while the earlier limiter also trusts X-Forwarded-For. Exploitation requires a reachable API and a weak or reused token; the default loopback binding and generated random token substantially reduce practical exposure.
Summary
What happened
Insufficient rate limiting in PinchTab 0.7.7 through 0.8.4 allows remote attackers to guess weak API tokens via repeated HTTP requests. The production handler chain omits RateLimitMiddleware through 0.8.3; in 0.8.4, the health route remains exempt, while the earlier limiter also trusts X-Forwarded-For. Exploitation requires a reachable API and a weak or reused token; the default loopback binding and generated random token substantially reduce practical exposure.
The record
- CVE
- CVE-2026-33621
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- PinchTab
- Product
- PinchTab
- Classifications
- CWE-770, CWE-290, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.7.7, < 0.8.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unthrottled health-route token-guessing proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo