CVE-2024-45489: Arc · Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 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
AI-suggested
- Immediately update Arc browsers to versions released after 2024-08-26 once patches become available to eliminate the vulnerability.
- Review and correct Firebase ACL configurations to ensure that boosts cannot be created or updated using another user's ID, enforcing strict access controls and least privilege principles.
- Implement monitoring and alerting for unusual boost creation or modification activities within Firebase to detect potential exploitation attempts.
- Conduct security audits of all JavaScript boosts and extensions deployed in the environment to verify their integrity and origin.
- Educate users and administrators about the risks of sharing boosts and the importance of secure configuration management.
- Employ Content Security Policy (CSP) headers and browser security features to limit the impact of arbitrary JavaScript execution if exploitation occurs.
- Maintain an incident response plan to quickly isolate and remediate compromised browsers or accounts if exploitation is detected.
Description
Arc before 2024-08-26 allows remote code execution in JavaScript boosts. Boosts that run JavaScript cannot be shared by default; however (because of misconfigured Firebase ACLs), it is possible to create or update a boost using another user's ID. This installs the boost in the victim's browser and runs arbitrary Javascript on that browser in a privileged context. NOTE: this is a no-action cloud vulnerability with zero affected users.