CVE-2026-130725: NocoDB before 2026.10.0 IDOR via Attachment Field Paths
NocoDB before 2026.10.0 contains an insecure direct object reference vulnerability that allows authenticated users to obtain signed download URLs for other bases' attachments by storing foreign attachment paths in their own rows via prepareNocoData. Attackers with write access to an attachment column can have convertAttachmentType or the attachment download endpoint sign the foreign path, reading cross-base files despite secure attachment mode.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be authenticated and have write access to an attachment column in a NocoDB row. Exploitation targets attachments stored in other bases, so the attacker also needs a foreign attachment path to submit.
Are deployments using secure attachment mode protected?
No. The issue can be exploited despite secure attachment mode because attachment-processing code or the download endpoint can sign a foreign attachment path.
What access does exploitation provide?
The attacker can obtain signed download URLs for attachments belonging to other bases and use those URLs to read the cross-base files. The provided data does not indicate integrity or availability impact.
How can administrators determine whether they are affected?
Instances running NocoDB versions before 2026.10.0 are affected according to the advisory data. Review whether authenticated users can write to attachment columns and whether they could supply paths referencing attachments from other bases.