Quota/Billing Bypass via Forged Bot-Mode Requests (Ultra Tier Affected) – Reported via Security Channel, Requesting Official Follow-up

Support Bug Reports
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

Hi everyone,
I’d like to raise awareness of an actively exploited billing security issue. In the spirit of responsible disclosure, I will not share any reproduction details in this post.
Summary: Cursor’s bot quota is intended exclusively for bot mode. However, a technique currently circulating allows IDE/Agent sessions to be disguised as bot-mode requests, thereby consuming the bot-channel model quota and bypassing normal quota deduction for the user’s subscription tier. The abuse affects not only free/trial accounts but also paid subscriptions, including the Ultra tier.
Current status: Based on my observations, the abuse is ongoing and spreading within the community. This means:
• Legitimate paying users — especially Ultra subscribers — are effectively subsidizing abusers’ usage;
• Cursor’s revenue and upstream model costs are being continuously drained;
• The longer this goes unaddressed, the higher the cost of remediation.
I submitted a full technical report through the official security channel on [date] [ticket ID, if available]. I would like to ask the team to:

  1. Confirm the issue has been acknowledged;
  2. Share progress or an estimated timeline for a fix;
  3. Publish an advisory describing the scope of impact once resolved.
    If other users have observed similar anomalies (e.g., abnormal quota consumption, inaccurate Dashboard metering), feel free to describe the symptoms below — but please do not share or link to the abuse method itself.
    Thanks.

Steps to Reproduce

none

Operating System

Windows 10/11

Version Information

Version: 3.18.25 (system setup)
VS Code Extension API: 1.128.0
Commit: 280eca2911f1774689696e5f1efa5a4f97a87af0
Date: 2026-08-31T23:08:02.261Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.22621

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Thanks for the report @gggggg. We’re looking into it and I’ll follow back up with you here.