CVE-2026-28280 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in github.com/jmpsec/osctrl. A fix is available for github.com/jmpsec/osctrl — see the affected versions and patch details below.
`osctrl-admin` has Stored Cross-Site Scripting (XSS) in On-Demand Query List
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28280.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/jmpsec/osctrlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A stored Cross-site Scripting (XSS) vulnerability exists in the osctrl-admin on-demand query list. A user with query-level permissions can inject arbitrary JavaScript via the query parameter when running an on-demand query. The payload is stored and executes in the browser of any user (including administrators) who visits the query list page. This can be chained with CSRF token extraction to escalate privileges and take actions as the logged in user.
Impact
An attacker with query-level permissions (the lowest privilege tier) can execute arbitrary JavaScript in the browsers of all users who view the query list. Depending on their level of access, it can lead to full platform compromise if an administrator executes the payload.
Patches
Fixed in osctrl v0.5.0. Users should upgrade immediately.
Workarounds
Restrict query-level permissions to trusted users. Monitor query list for suspicious payloads. Review osctrl user accounts for unauthorized administrators.
References
Credits
Leon Johnson and Kwangyun Keum from TikTok USDS JV Offensive Security Operations (Offensive Privacy Team)
https://github.com/Kwangyun → @Kwangyun
https://github.com/sho-luv → @sho-luv
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jmpsec/osctrl | all versions | 0.5.0go get github.com/jmpsec/osctrl@v0.5.0 |
Affected Products
osctrljmpsecDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jmpsec/osctrl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jmpsec/osctrl to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28280 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-28280 in your dependencies?
Find it across Go, including transitive dependencies.