A flaw was found in the file-xmc plugin in GIMP. When processing a specially crafted XMC image file, the plugin does not properly validate the comment subtype before using it as an array index. This missing validation leads to out-of-bounds memory access, invalid free and use-after-free issues. This vulnerability can result in an application crash, leading to a denial of service, or potentially allow for arbitrary code execution.
Command injection vulnerability in the affected interface of AOS-10 or AOS-8 could allow an authenticated remote attacker to perform command injection only on certain impacted devices. Successful exploitation could allow an attacker to execute unauthorized arbitrary commands with the privileges of the affected mechanism on the underlying operating system.
An unauthenticated buffer overflow vulnerability exists in the underlying operating system of AOS-10 or AOS-8 and could allow an unauthenticated adjacent attacker to conduct a denial of service attack. Successful exploitation could allow an attacker to disrupt the availability of the affected system, with a limited impact to the integrity of the affected component.
Vulnerabilities in the PAPI protocol of AOS-10 could allow an unauthenticated remote attacker to circumvent existing authentication controls. Successful exploitation could allow an attacker to gain administrative access, modify system configurations, and access or manipulate sensitive data.
LVRTC eParakstītājs 3.0 version 1.10.0 for macOS contains a vulnerability that allows an unauthenticated remote attacker to execute arbitrary commands with the privileges of the current user. This occurs when a user opens a specially crafted PDF filename and selects the Send option. The application improperly embeds the attachment path in AppleScript without sanitizing the syntax, enabling command injection via AppleScript do shell script expressions.
Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute contains a vulnerability that allows an unauthenticated remote attacker to induce HTTP GET requests from a user's workstation by tricking the user into opening a crafted signed eDOC file. The vulnerability involves automatic certificate validation that retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL and follows redirects without destination restrictions, enabling blind Server-Side Request Forgery (SSRF) to internal network services. Additionally, the software allows unrestricted loading of local file URIs, which can cause unbounded memory buffering leading to Denial of Service (OutOfMemoryError). In automated server verification pipelines with UI:N, the impact is rated high with a CVSS score of 8.8.
Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute for Linux contains a command injection vulnerability. An unauthenticated remote attacker can execute arbitrary commands with the privileges of the current user by tricking the user into opening a signed PDF with a crafted filename and choosing to open it with Adobe Reader. The vulnerability arises because the application embeds the filename in a shell command without properly neutralizing shell command substitution.
Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute contains a vulnerability that allows an unauthenticated remote attacker to induce HTTP GET requests from a user's workstation by tricking the user into opening a crafted signed eDOC file. The automatic certificate validation process follows signer-controlled Authority Information Access (AIA) caIssuers URLs and redirects without destination restrictions, enabling blind Server-Side Request Forgery (SSRF) to internal network services. Additionally, the software can load local file URIs without restriction, causing unbounded memory buffering and resulting in a Denial of Service (OutOfMemoryError). The vulnerability has a CVSS 3.1 base score of 6.1 (medium severity).
The Apache Iggy Go SDK versions from 0.5.0 up to but not including 0.10.0 contain an insufficient session expiration vulnerability. The CreatePersonalAccessToken method incorrectly encodes the token expiry time, causing the server to interpret the expiry as approximately four billion times longer than intended. This results in tokens remaining valid far beyond their expected lifetime. Version 0.10.0 addresses this issue. Users should upgrade and revoke any tokens created with affected versions to mitigate the risk.
NocoDB versions before 2026.10.0 have an insecure direct object reference (IDOR) vulnerability. Authenticated users with write access to attachment columns can exploit this flaw to obtain signed download URLs for attachments belonging to other bases by inserting foreign attachment paths into their own data rows. This allows reading of cross-base files even when secure attachment mode is enabled.
NocoDB versions prior to 2026.10.1 have an authentication bypass vulnerability. This flaw allows attackers holding OAuth tokens, which are signed with the instance JWT secret, to escalate their privileges and act as full authenticated sessions. By presenting a narrowly scoped OAuth token to various authentication mechanisms, attackers can gain the full privileges of the granting user.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to determine pending invitees by observing distinct sign-in error messages. This occurs because the validateUser function skips password checks for saltless invited accounts, enabling attackers to confirm the existence of an email address associated with an account.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to distinguish registered email addresses by analyzing different responses from the sign-up endpoint. This includes identifying existing accounts and pending Enterprise invitations, even when sign-up is restricted to invite-only.
NocoDB versions from 0.301.4 up to but not including 2026.10.1 have a vulnerability where the nc_token session cookie is set via script in the Enterprise useGlobal composable without the Secure attribute. This omission allows attackers positioned on the network to capture the session token by observing or inducing plain-HTTP requests to HTTPS instances, enabling session impersonation until the token expires.
NocoDB versions from 0.301.4 up to but not including 2026.10.0 have an information disclosure vulnerability. Authenticated workspace viewers can access pending invitation tokens via the workspace member list. These tokens can be redeemed by attackers to claim invited accounts and escalate privileges to roles such as workspace owner.
NocoDB versions prior to 2026.10.1 have a credential exposure vulnerability in the connection-test endpoint. Authorized integration users can manipulate connection parameters to redirect stored credentials to an attacker-controlled server. This allows attackers to capture PostgreSQL md5 or MySQL handshake data, which can be cracked offline to recover database passwords.
NocoDB versions prior to 2026.10.1 have an information disclosure vulnerability that permits unauthenticated users holding shared view links to access hidden column data. By exploiting the group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and confirm the existence of such columns.
NocoDB versions prior to 2026.10.0 contain an account takeover vulnerability. Users with the base creator role can exploit this flaw by resending base invitations to generate new invite tokens, which they can then read from the base member list. This allows them to reset the password of other users, including owner or super admin accounts, effectively hijacking those accounts.
NocoDB versions prior to 2026.10.1 contain an SQL injection vulnerability due to improper escaping of backslashes in select-field option titles embedded into MySQL or MariaDB enum/set column definitions. This flaw allows a base creator or owner to manipulate option titles to inject malicious ALTER TABLE statements, potentially modifying database schema elements such as columns and indexes.
NocoDB versions from 2026.07.0 up to but not including 2026.10.0 contain an SQL injection vulnerability. This flaw allows users with the Creator role to inject SQL via unescaped backslashes in the DATETIME_FORMAT formula's format argument on MySQL-backed databases. Exploitation can lead to unauthorized reading of data accessible by the database user, including data outside the intended base.