ScreenTinker before 3.2.4 contains a stored cross-site scripting vulnerability in the GET /api/kiosk/:id/render endpoint that allows users with kiosk page edit rights to store javascript: URLs in page buttons. Attackers can trigger script execution in the dashboard origin when an administrator activates the button, hijacking the victim's session and taking full control of the instance.
Multiple vulnerabilities have been identified in JetBrains TeamCity, a Continuous Integration and Deployment tool used by developers and DevOps engineers. These issues affect versions prior to 2026.1.3 and the version 2026.1.3 itself. A fixed version, 2026.1.3, is available to address these vulnerabilities.
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, _maybe_update_replicated_unlocked in mareforma/db/core.py does not check t_invalid in its new-claim gate, peer-selection query, or final update, so a claim marked invalid by a signed contradiction verdict can still be promoted to REPLICATED through convergence. The invalidated claim can also act as the corroborating peer that promotes an honest claim, bypassing the trust ladder's terminal refutation state. This issue is fixed in version 0.3.8.
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, verify_bundle in mareforma/export_bundle.py validates the outer DSSE envelope and exporter-signed subject digests, but JSONLDExporter._claim_node in mareforma/exporters/jsonld.py supplies no signatureBundle for individual claims. Because the exporter signs both the predicate nodes and their digest list, the check proves only internal bundle consistency and allows claims with missing, invalid, or forged asserter signatures to be accepted as authentic. This issue is fixed in version 0.3.8.
CVE-2026-71533 is a vulnerability in mareforma versions 0.3.7 where the function search_claims fails to perform cryptographic signature verification on certain data rows. This allows forged or tampered replicated or established rows to be returned without detection, bypassing the intended high-trust verification. The issue is fixed in version 0.3.8.
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, restore logic in mareforma/db/restore.py derives transparency_logged from the unsigned rekor.uuid field inside signature_bundle without requiring a verified claim-bound rekor_inclusions entry, so an attacker who modifies claims.toml can falsely make a claim eligible for REPLICATED convergence. The same logic resets signed claims in non-Rekor graphs from transparency_logged 1 to 0 after restore, permanently preventing convergence because no Rekor refresh is configured. This issue is fixed in version 0.3.8.
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.7, the _maybe_update_replicated_unlocked convergence path in mareforma/db/core.py uses generated_by labels without requiring a valid signature_bundle from a distinct enrolled signer, so an unsigned claim written to a shared graph can converge with a signed peer and be promoted to REPLICATED. The forged trust state is returned by queries requiring REPLICATED support, allowing false multi-party endorsement signals to reach downstream consumers. This issue is fixed in version 0.3.7.
This vulnerability concerns the ALSA usx2y driver component, specifically its handling of DSP load retries after a failure. The issue involves refusing a retried DSP load following a failure, potentially impacting the affected software versions 3.0 and 4.0. No detailed impact or exploitation information is provided.
A use-after-free vulnerability exists in the ALSA bcd2000 driver related to MIDI URBs when a file is closed. This flaw can lead to memory corruption or instability in affected Microsoft products. The vulnerability is identified as CVE-2026-99318 and affects versions 3.0 and 4.0 of the product.
This entry references a vulnerability identified as CVE-2026-99317 related to ALSA hardware-dependent (hwdep) components, specifically concerning serialization of DSP load requests. The information provided is minimal and does not include technical details about the nature of the vulnerability, its impact, or exploitation methods. The affected versions are 3.0 and 4.0. No CVSS score or vendor advisory details are available.
This vulnerability involves the ALSA usx2y driver where idle USB Request Blocks (URBs) are not initialized before submitting audio streams. The issue is identified in Microsoft products with affected versions 3.0 and 4.0. No CVSS score or detailed impact information is provided, and no known exploits are reported in the wild.
A vulnerability identified as CVE-2026-99315 affects Microsoft products version 3.0 and 4.0, involving a NULL pointer dereference in the ALSA us122l component during hardware-dependent open and release operations. The issue could potentially cause application crashes or denial of service. No CVSS score or detailed impact information is provided.
A vulnerability identified as CVE-2026-99314 involves a missing NULL check in the usb_stream_hwdep_mmap() function within the ALSA us122l component. The issue affects Microsoft products with versions 3.0 and 4.0. No CVSS score or detailed impact information is provided, and no known exploits are reported in the wild.
This vulnerability involves the KVM (Kernel-based Virtual Machine) component for x86 architectures, where the MMU (Memory Management Unit) context is unconditionally reset when emulating the INIT instruction. The issue affects Microsoft products with versions 3.0 and 4.0. No CVSS score or detailed impact information is provided.
Info-ZIP Zip versions 3.0 and 4.0 contain a vulnerability that allows OS command injection when an attacker can control the command line input. This vulnerability is identified as CVE-2026-130335 and is related to improper handling of command line parameters.
The ISO-2022-CN-EXT decoder in Microsoft products version 3.0 and 4.0 may read beyond the intended input buffer. This vulnerability relates to improper input handling that could lead to out-of-bounds reads.
Three distinct cyberattack campaigns are targeting US trucking and logistics companies by impersonating trusted digital platforms used in routine operations. These campaigns use fake portals and phishing infrastructure to harvest credentials, personal data, and fuel card information, distribute malware including Node.js backdoors, and deploy remote access tools like MeshCentral and CastleRAT. They exploit common workflows such as carrier verification, broker onboarding, and freight booking to compromise operational systems and extract sensitive data like BitLocker recovery keys.
keystore-go is a Go implementation of the Java KeyStore encoder and decoder. In 2.1.0 and earlier, keystore.Decode in decoder.go does not check the error returned when reading the trailing SHA-1 integrity digest and bounds its comparison by the length of the digest actually read. If an attacker with write access removes the final 20-byte digest from a modified JKS file, the empty actual digest causes the comparison loop to execute zero times and Decode returns the parsed keystore without an error. For certificate-only stores using TrustedCertificateEntry values, this bypasses both tamper detection and password verification, allowing trusted CA certificates to be added or replaced without knowing the keystore password and potentially enabling interception or modification of TLS connections that trust the forged CA. This issue is fixed in version 3.0.0.
CVE-2026-63411 is a critical code injection vulnerability in janephp versions prior to 7.12.0. The issue arises because the Jane open-api-3 generator includes OpenAPI parameter descriptions verbatim in generated PHP client method docblocks. If a parameter description contains a PHPDoc closing delimiter, it can prematurely terminate the comment and inject attacker-controlled PHP code into the class body, including an __construct method that executes upon client instantiation. This allows arbitrary PHP code execution with the privileges of the consuming application. The vulnerability is fixed in version 7.12.0.
Jane is a set of PHP libraries that generates models and API clients from JSON Schema and OpenAPI specifications. Prior to 7.12.0, the Jane open-api-3 generator emits an OpenAPI query parameter name verbatim as an array key in generated Client/Endpoint method docblocks. A query parameter name containing a PHPDoc closing delimiter can terminate the comment early and place attacker-controlled PHP in class-body position, including an __construct method that runs when the generated Client is instantiated. Exploitation requires generating a client from an attacker-influenced OpenAPI document and then using the generated SDK, and can execute arbitrary PHP with the consuming application's privileges. This issue is fixed in version 7.12.0.