CVE-2023-26141 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in sidekiq. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for sidekiq — see the affected versions and patch details below.
sidekiq Denial of Service vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2023-26141.
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
sidekiq💎sidekiqReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Versions of the package sidekiq before 7.1.3 and 6.5.10 are vulnerable to Denial of Service (DoS) due to insufficient checks in the dashboard-charts.js file. An attacker can exploit this vulnerability by manipulating the localStorage value which will cause excessive polling requests.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | sidekiq | ≥ 7.0.0&&< 7.1.3 | 7.1.3bundle update sidekiq --conservative |
| 💎RubyGems | sidekiq | all versions | 6.5.10bundle update sidekiq --conservative |
Affected Products
sidekiqcontribsysResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sidekiq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sidekiq to 7.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26141 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Satellite 6.14 for RHEL 8 | rubygem-sidekiq-0:6.5.12-1.el8sat | RHSA-2024:0797 |
Frequently Asked Questions
Is CVE-2023-26141 in your dependencies?
Find it across RubyGems, including transitive dependencies.