GHSA-r8c2-2qwq-94p6 — rollbar
Fix: rollbar/rollbar.js@d717defGHSA-r8c2-2qwq-94p6 is a CWE-1321 vulnerability in rollbar. A fix is available for rollbar — see the affected versions and patch details below.
rollbar vulnerable to prototype pollution
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 GHSA-r8c2-2qwq-94p6.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
rollbarnpmDescription
Impact
Prototype pollution potential with the utility function rollbar/src/utility.set(). No impact when using the published public interface.
If application code directly imports set from rollbar/src/utility and then calls set with untrusted input in the second argument, it is vulnerable to prototype pollution.
POC:
const obj = {};
require("rollbar/src/utility").set(obj, "__proto__.polluted", "vulnerable");
console.log({}.polluted !== undefined ? '[POLLUTION_TRIGGERED]':'');
Patches
Fixed in version 2.26.5 and 3.0.0-beta5.
Workarounds
If application code directly imports set from rollbar/src/utility, ensure that the second argument does not receive untrusted input.
References
https://github.com/rollbar/rollbar.js/issues/1333#issuecomment-3353720946
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | rollbar | all versions | 2.26.5npm install rollbar@2.26.5 |
| 📦npm | rollbar | ≥ 3.0.0-alpha1&&< 3.0.0-beta5 | 3.0.0-beta5npm install rollbar@3.0.0-beta5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rollbar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rollbar to 2.26.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r8c2-2qwq-94p6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r8c2-2qwq-94p6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r8c2-2qwq-94p6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r8c2-2qwq-94p6 in your dependencies?
O3 Security finds GHSA-r8c2-2qwq-94p6 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.