CVE-2024-36583: accessor · Prototype Pollution
Affects accessorSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npm@byondreal/accessorpkg:npm/@byondreal/accessorOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate auditing of all software dependencies to identify usage of @byondreal/accessor package version 1.0.0 or earlier.
- Implement strict input validation and sanitization to reduce the risk of prototype pollution attacks where possible.
- Monitor official repositories and security advisories for patches or updates addressing this vulnerability and apply them promptly once available.
- Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules designed to detect and block prototype pollution attack patterns.
- Use dependency scanning tools integrated into CI/CD pipelines to detect vulnerable package versions automatically.
- Consider isolating or sandboxing components that use this package to limit the blast radius of potential exploitation.
- Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities in custom code.
- If immediate patching is not possible, consider temporary mitigation by restricting network exposure of affected services and limiting access to trusted users only.
Description
A Prototype Pollution issue in byondreal accessor <= 1.0.0 allows an attacker to execute arbitrary code via @byondreal/accessor/index.