The Apache Airflow Microsoft Azure provider versions 10.2.0 through 15.3.0 include a vulnerability in the S3ToAzureBlobStorageOperator where TLS certificate verification for connections to Amazon S3 is disabled by default. This allows a network attacker to intercept and manipulate data transferred between Airflow workers and S3. The issue is fixed in version 15.3.1, which respects the AWS connection's TLS verification settings.
A missing authorization vulnerability in Apache Iggy server prior to version 0.9.0 allows any authenticated user, regardless of permissions, to download sensitive diagnostic archives. These archives include server logs, process lists, file system listings, and runtime configuration containing secrets such as HTTP JWT signing keys. Exploitation could enable token forgery for any account, including root. The issue is fixed in version 0.10.0.
The WP Delicious – Recipe Plugin for Food Bloggers WordPress plugin (formerly Delicious Recipes) is vulnerable to stored cross-site scripting (XSS) via the 'recipeTitle' parameter in all versions up to and including 1.10.10. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and output escaping, allowing crafted payloads to bypass WordPress core filtering mechanisms.
The WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'details[].icon' parameter. This affects all versions up to and including 1.10.11. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and output escaping, with the payload bypassing wp_kses_post due to Gutenberg's JSON serialization and rendering process.
Apache Iggy server versions through 0.9.0 have an insufficient session expiration vulnerability in their HTTP transport. The vulnerability arises because JSON Web Tokens (JWTs) identify users only by numeric user ID, and new users receive the lowest available ID. If an administrator deletes a user, the deleted user's unexpired or refreshed token can authenticate as a new user who receives the same ID, inheriting that user's permissions. This affects only deployments with HTTP enabled. Upgrading to version 0.10.0 resolves the issue.
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.
This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.
Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server. If Apache Iggy 0.9.0 started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, it generated a root password and wrote it to the server log file, which is enabled by default. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) let a user with only the read_servers permission download the server log files. That user could read the generated root password and log in as root.
This issue affects Apache Iggy: 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Version 0.10.0 never generates a root password, and the snapshot requires the manage_servers permission. If a 0.9.0 server generated its root password, change that password.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0 for macOS allows an unauthenticated remote
attacker to execute arbitrary commands with the privileges of the current user
by convincing the user to open a PDF with a crafted filename and select Send.
The application embeds the attachment path in AppleScript source without
neutralizing AppleScript syntax, allowing injected do shell script expressions
to execute.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.
NocoDB versions before 2026.10.1 have an authentication bypass vulnerability where OAuth tokens signed with the instance JWT secret can be used to gain full user session privileges. This allows attackers with a narrowly scoped OAuth token to escalate their access by presenting the token to various authentication mechanisms within NocoDB.
NocoDB versions prior to 2026.10.0 contain an authorization bypass vulnerability that allows authenticated users with write access to attachment columns to obtain signed download URLs for attachments belonging to other bases. This occurs due to insecure direct object references via user-controlled foreign attachment paths, enabling cross-base file access despite secure attachment mode.
NocoDB before 2026.10.1 contains a user enumeration vulnerability that allows unauthenticated attackers to determine registered email addresses by observing differing sign-up endpoint responses. Attackers can submit addresses to signup in users.service.ts and compare error messages to identify existing accounts and pending Enterprise invitations, even under invite-only signup.
NocoDB versions before 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to identify pending invitees by observing distinct sign-in error messages. This occurs because the authentication service skips password comparison for saltless invited accounts, confirming the existence of an account associated with the email address.
NocoDB from 0.301.4 before 2026.10.1 writes the nc_token session cookie from script in the Enterprise useGlobal composable without the Secure attribute. Network-positioned attackers can observe or induce plain-HTTP requests to https instances to capture the session token and impersonate the victim until expiry.
NocoDB before 2026.10.0 contains an improper access control vulnerability that allows Creator-role users to attach NocoDB's internal database by supplying is_meta and is_local flags. Attackers can create sources or bases with these flags to expose user, token and integration tables, then read and modify records including user roles.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated users holding shared view links to access hidden columns. By exploiting the public group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and existence. This vulnerability is fixed in version 2026.10.1.
NocoDB before 2026.10.0 contains an account takeover vulnerability that allows users with the base creator role to hijack other accounts by resending base invitations. Attackers can trigger baseUserInviteResend to mint a new invite_token, read it from the base member list, and reset the victim's password through signup, taking over owner or super admin accounts.
NocoDB before 2026.10.0 contains an information disclosure vulnerability that allows unauthenticated attackers to read hidden columns by supplying comma-separated group-by column lists. Attackers with a shared view link can pair a visible and hidden column to bypass restrictSharedViewColumnReferences and retrieve hidden values tied to individual rows.
NocoDB versions before 2026.10.1 have an SQL injection vulnerability due to improper escaping of backslashes in select-field option titles embedded in MySQL or MariaDB enum/set column definitions. This flaw allows a base creator or owner to manipulate option titles to inject malicious ALTER TABLE commands, potentially modifying database schema elements such as columns and indexes.