Authenticated database-write outage via unsafe deep merge
Published Jan 28, 2026 · Updated Jan 28, 2026
Prototype pollution in NocoDB before 0.301.0 allows remote authenticated users to halt all database writes via a crafted connection-test request. The deepMerge function recursively merges the endpoint body without filtering proto, constructor, or prototype keys, allowing Object.prototype modification. Org-level-creator permissions are required, and successful pollution leaves database writes unavailable for all users until the server process restarts.
Summary
What happened
Prototype pollution in NocoDB before 0.301.0 allows remote authenticated users to halt all database writes via a crafted connection-test request. The deepMerge function recursively merges the endpoint body without filtering proto, constructor, or prototype keys, allowing Object.prototype modification. Org-level-creator permissions are required, and successful pollution leaves database writes unavailable for all users until the server process restarts.
The record
- CVE
- CVE-2026-24766
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- NocoDB
- Product
- NocoDB
- Classifications
- CWE-1321, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.301.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-95ff-46g6-6gw9 prototype-pollution requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo