CVE-2025-65096: rommapp romm · Improper Access Control
Affects rommapp rommSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.4.1 when convenient.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.4.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Dec 2025
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
Upgrade rommapp/romm to 4.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrommapp/rommpkg:github/rommapp/rommOther 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
To mitigate this vulnerability, organizations should immediately upgrade all RomM instances to version 4.4.1 or later, where the issue is fixed. If upgrading is not immediately possible, implement network-level access controls to restrict API access to trusted users or internal networks only. Review and audit API endpoints to ensure proper access control and ownership verification are enforced. Employ rate limiting and monitoring to detect unusual access patterns that may indicate exploitation attempts. Educate users about the importance of not sharing collection IDs publicly. Additionally, conduct a privacy impact assessment to identify any exposed data and notify affected users if a breach is suspected. Integrate security testing in the development lifecycle to prevent similar authorization bypass issues in future releases.
Description
RomM (ROM Manager) allows users to scan, enrich, browse and play their game collections with a clean and responsive interface. Prior to 4.4.1 and 4.4.1-beta.2, users can read private collections / smart collections belonging to other users by directly accessing their IDs via API. No ownership verification or checking if the collection is public/private before returning collection data. This vulnerability is fixed in 4.4.1 and 4.4.1-beta.2.