CVE-2026-126286 in NocoDB
Summary
by MITRE • 11/13/2026
NocoDB before 2026.08.0 contains a reflected cross-site scripting vulnerability in PageLeavingWarning.vue that allows unauthenticated attackers to execute script by embedding an ASCII control character in the ncRedirectUrl scheme. Attackers can send a crafted link that bypasses the scheme check and reaches the anchor href or window.location, stealing the session token from localStorage for account takeover.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in NocoDB versions prior to 2026.08.0 represents a critical security flaw rooted in improper input validation within the client-side application logic. Specifically, the defect resides in the PageLeavingWarning.vue component, which is responsible for handling navigation events and redirect URLs. The core technical issue involves an insufficient sanitization of user-supplied data passed through the ncRedirectUrl parameter. While the application attempts to enforce security by checking URL schemes, it fails to adequately filter or escape ASCII control characters embedded within these strings. This oversight allows attackers to construct malicious payloads that bypass standard scheme validation checks, effectively tricking the browser into interpreting a controlled string as a valid navigation target rather than plain text data.
From an operational perspective, this reflected cross-site scripting vulnerability enables unauthenticated actors to execute arbitrary JavaScript code in the context of the victim's browser session. The attack vector typically involves sending a crafted link containing malicious script tags or event handlers disguised within the redirect URL parameter. When a user clicks this link, the application processes the input without proper encoding, leading to the injection and execution of the attacker-controlled scripts. This mechanism is particularly dangerous because it does not require prior authentication, allowing any internet user with access to the NocoDB instance to initiate the attack sequence against authenticated users who visit the malicious URL.
The impact of this vulnerability extends beyond simple script execution, posing a severe risk to account security and data integrity. By leveraging the executed JavaScript code, attackers can interact with the browser's local storage API to extract sensitive session tokens stored in localStorage. These tokens are often used for maintaining user sessions without requiring repeated logins. Once an attacker obtains these credentials, they can impersonate the victim within the NocoDB environment, leading to a complete account takeover. This compromise allows the adversary to access, modify, or delete project data, view sensitive information belonging to other users, and potentially escalate privileges if additional vulnerabilities exist in conjunction with this flaw.
This vulnerability aligns closely with CWE-79, which classifies improper neutralization of input during web page generation as a cross-site scripting weakness. Furthermore, the exploitation technique maps directly to MITRE ATT&CK techniques T1059.007 for JavaScript execution and T1539 for Steal Web Session Cookie, highlighting the direct path from initial access through client-side script injection to credential theft. The failure lies in the lack of robust output encoding and strict allow-listing of URL schemes, which are fundamental principles in secure web development practices recommended by OWASP.
To mitigate this vulnerability, organizations running NocoDB must upgrade immediately to version 2026.08.0 or later, where these input validation checks have been hardened. For environments unable to patch instantly, implementing a Web Application Firewall with rules that detect and block ASCII control characters within URL parameters can provide temporary relief. Additionally, developers should ensure that all user-supplied data is strictly validated against an allow-list of safe schemes before being passed to navigation functions like window.location or anchor href attributes. Enabling Content Security Policy headers that restrict script execution sources can also help mitigate the impact by preventing the injection and subsequent execution of malicious scripts from unauthorized domains.