PAX Technology Q80 Application Installer Signature Verification Bypass Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of PAX Technology Q80. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the application installer. The issue results from the lack of proper verification of a cryptographic signature before installing an application. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-30585.
CVE-2026-47192 is a medium severity vulnerability in Siemens kas, a setup tool for bitbake-based projects. Versions from 4.8 up to but not including 5.3 improperly verify cryptographic signatures by processing repositories before validating their signatures. Under specific conditions involving repository control, configuration includes, and key management, an attacker could replace a legitimate repository with a malicious one. The issue is fixed in kas version 5.3. A workaround involves pinning the expected signature key via its fingerprint.
CVE-2026-47191 is a vulnerability in Siemens kas, a setup tool for bitbake-based projects, affecting versions prior to 5.3. The issue involves improper verification of cryptographic signatures when relying solely on git commit IDs (SHA-1 or SHA-256) to validate repository state. This can allow an attacker who controls the repository to trick users into checking out malicious branches with the same name. The vulnerability primarily impacts SHA-256 commit IDs due to the possibility of hash collisions with SHA-1. Version 5.3 addresses this issue. Workarounds include avoiding sole reliance on commit IDs, validating cryptographically signed commits or tags, or using mirrored repositories with verified integrity.
A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to serve malicious module content that cannot be detected by evaluating the transparency log. All tiles are now correctly verified against their parents. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidy
A malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log. This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating the transparency log. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidy
Zohocorp ManageEngine Password Manager Pro versions before 13232 and PAM360 versions before 8551 are vulnerable to an authentication bypass vulnerability due to improper SAML validation.
CVE-2026-48791 is a vulnerability in sigstore-java version 2.0.0 where verification of the integrated Rekor entry time against the Fulcio certificate was erroneously removed. This flaw allows a malicious actor who has exfiltrated a temporary private key used during signing to reuse an old Fulcio certificate without needing direct access to the user's credentials. The issue is fixed in version 2.1.0, which reintroduces and enhances this verification step according to the Sigstore verification specification.
CVE-2026-68757 is a high-severity vulnerability in JFrog Artifactory involving improper verification of cryptographic signatures in SAML responses. An attacker with access to a valid SAML response may impersonate another user under specific conditions. The flaw affects versions prior to 7.146.35 and versions from 7.161.0 up to but not including 7.161.16. Fixed versions 7.146.35 and 7.161.16 address this issue.
SAP Approuter does not consistently enforce integrity verification on certain session-related request headers under specific conditions. An attacker with low privileges could send a specially crafted request that bypasses the integrity check and loads another user's session context. Successful exploitation requires the attacker to have previously observed matching session values out-of-band, which makes the attack complex to execute. This could result in a high impact on confidentiality and a low impact on integrity. There is no impact on availability.
Pega Platform versions 8.5.0 through 25.1.2 are affected by an improper validation of cryptographic signatures that may allow an attacker to bypass security controls.
Improper verification of cryptographic signature and Improper Check for Unusual or Exceptional Conditions vulnerability in Estonian Information System Authority (RIA) libdigidocpp, DigiDoc4, DigiDoc on Android, and DigiDoc on iOS. This issue affects libdigidocpp: from 4.1.0 before 4.2.1; DigiDoc4: from 4.7.0 before 4.8.2; DigiDoc on Android: from 2.7.0 before 2.7.2; DigiDoc on iOS: from 2.8.0 before 2.8.1.
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check, so a malicious or compromised block producer can set them to reach the required quorum while gathering fewer genuine validator signatures than the protocol demands. As a result, nodes that import or intercept the header accept it as correctly signed without a real two-thirds quorum, weakening consensus safety and undermining finality. This issue is fixed in version 1.7.20.
The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access.
Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.