Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute for Linux allows an unauthenticated
remote attacker to execute arbitrary commands with the privileges of the
current user by convincing the user to open and validate a signed PDF with a
crafted filename and select Open with Adobe Reader. The application embeds the
filename in a sh -c command without neutralizing shell command substitution.
A flaw was found in lldpd. The service fails to verify that Link Layer Discovery Protocol - Media Endpoint Discovery (LLDP-MED) location records received from network neighbors match their declared lengths. An adjacent attacker on the local network can exploit this flaw by sending crafted packets, causing client applications using the liblldpctl library to read past buffer boundaries when parsing location data. This issue can lead to an information disclosure of adjacent process memory.
Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account's permissions. Only deployments with HTTP enabled are affected.
This issue affects Apache Iggy: through 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root.
This issue affects Apache Iggy: before 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.
The WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'recipeTitle' parameter in all versions up to, and including, 1.10.10 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. WordPress core's block-attribute kses pass strips HTML tags but preserves bare double-quote characters, allowing a payload such as x" onerror="alert(1) to survive both the save pipeline and the render-time strip_tags() call, breaking out of the alt attribute of the rendered img element.
The WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'details[].icon' parameter in all versions up to, and including, 1.10.11 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload bypasses wp_kses_post on save because Gutenberg serializes block attribute JSON with JSON_HEX_QUOT, encoding double-quotes as \u0022 so no raw quote or angle bracket appears in post_content; parse_blocks() restores the literal quote at render time, producing the HTML attribute breakout.
The Otter Blocks WordPress plugin before 3.2.10 does not use URL-aware escaping when it resolves its dynamic data tags inside HTML attributes, which could allow unauthenticated users to post comments containing links that execute arbitrary JavaScript when clicked, for example by a logged-in administrator.
WLA DX versions 9.7 through 10.7 have a stack-based buffer overflow vulnerability in the parse_data_blocks() function located in wlalink/analyze.c. This flaw occurs because the function copies section namespaces without proper length checks, allowing an attacker to supply a crafted object or library file with a namespace longer than 255 bytes or unterminated. This can overflow the 256-byte stack buffer during linking.
A CRLF injection vulnerability in GitHub Enterprise Server allowed users with write access to bypass branch protections and update branches or tags via specially crafted input during pull request conflict resolution. This issue affected all versions prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. The vulnerability was responsibly disclosed through the GitHub Bug Bounty program.
A server-side request forgery (SSRF) vulnerability in GitHub Enterprise Server allowed an authenticated user with repository write access to send requests to internal services via Slack webhook validity checks. Exploitation required Secret Protection features with secret scanning and validity checks for partner patterns enabled. This vulnerability affected all versions prior to 3.23 and was fixed in versions 3.22.5, 3.21.10, and 3.20.12. It was reported through the GitHub Bug Bounty program.
A vulnerability in GitHub Enterprise Server prior to version 3.23 allowed an authenticated organization member to bypass SSH certificate authentication and access another user's private repositories. Exploitation required the use of built-in authentication and a valid SSH certificate issued by a trusted certificate authority. The issue was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5.
A vulnerability in GitHub Enterprise Server prior to version 3.23 allows a site administrator to modify files on the appliance host with root privileges and disclose private repository data. This occurs due to improper path validation in the handling of a crafted pre-receive hook environment. The issue was addressed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5.
A command injection vulnerability in GitHub Enterprise Server allowed authenticated site administrators in clustered deployments to execute arbitrary commands as the host git user on peer Git server nodes outside the pre-receive hook sandbox. This required a custom pre-receive hook environment and at least one peer Git server node. The issue affected all versions prior to 3.23 and was fixed in versions 3.22.5, 3.21.10, 3.20.12, and 3.19.16.
An incorrect authorization vulnerability in GitHub Enterprise Server allowed an authenticated user with a numeric user ID matching an enterprise's numeric ID to manage that enterprise's GitHub Apps and generate private keys without being a member of the enterprise. This flaw was due to ownership checks comparing numeric IDs without verifying the owner's account type. Exploitation required control of a session for the colliding user account and an enterprise-owned GitHub App. The vulnerability affected supported GitHub Enterprise Server versions prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5.
A hard-coded cryptographic key vulnerability in ASUS Control Center Express allows remote attackers to gain administrative privileges by forging authentication tokens. This critical flaw enables unauthorized access without user interaction or privileges. The vulnerability is identified as CVE-2026-114202 with a CVSS 4.0 score of 10.0, indicating maximum severity. No affected versions or patch information are provided in the available data.
A vulnerability in GitHub Enterprise Server allowed authenticated users to bypass authorization controls and read review-thread data from private repositories they could not normally access. The flaw involved the thread-preview endpoint resolving user-supplied review-thread identifiers without restricting them to the authorized pull request context. This exposed private file paths, source-code excerpts, commit identifiers, and line metadata. The issue affected versions in the 3.21 and 3.22 series and was fixed in 3.21.10 and 3.22.5.
A stored cross-site scripting vulnerability was identified in GitHub Enterprise Server that allowed an organization member with permission to manage custom-property definitions and edit property values to add an attacker-controlled SSH authentication key to the personal account of another member through HTML stored in a single-select custom-property option. Exploitation required another definition manager in the same organization to attempt to remove the poisoned option while it was in use and save the definition with a valid sudo session. Repository access through the added key depended on the permissions of the victim and independent authorization controls. This vulnerability affected supported GitHub Enterprise Server prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.