Skip to main content
CVE-2024-36573VulnerabilityPublished Updated

CVE-2024-36573: obx · n/a

Affects obxSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.0.4 as a priority.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade @almela/obx to 0.0.4.

Affected software

ProductAffectedFixed in
npm@almela/obxpkg:npm/@almela/obxOther threatsAffected
  • <0.0.4
Fixed in
  • 0.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate code review and audit: Identify all instances where almela obx is used within your codebase and assess the version in use. 2. 3. Temporary workarounds: Until a patch is released, implement input validation and sanitization to prevent untrusted data from influencing object prototypes. 4. Restrict prototype modification: Use JavaScript techniques such as Object.freeze() or Object.seal() on critical objects to prevent prototype pollution. 5. Employ runtime protection: Utilize application security tools or runtime application self-protection (RASP) solutions that can detect and block prototype pollution attempts. 6. Monitor logs and behavior: Set up alerts for unusual object property changes or suspicious code execution patterns in environments using almela obx. 7. Limit exposure: Restrict network access to services using the vulnerable library to trusted sources only. 8. Educate developers: Raise awareness among development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities.

Description

almela obx before v.0.0.4 has a Prototype Pollution issue which allows arbitrary code execution via the obx/build/index.js:656), reduce (@almela/obx/build/index.js:470), Object.set (obx/build/index.js:269) component.

References

Community reviews

Loading reviews…