The SAP Cloud SDK for Python contains an improper cryptographic signature verification vulnerability (CWE-347) in IASContextProvider, the runtime-context provider registered by default via bootstrap(app).IASContextProvider extracted the app_tid, sap_gtid and user_uuid claims from the IAS JWT in the Authorization header using an unverified decoder and wrote them into the request-scoped RuntimeContext without validating the token signature. A remote caller could submit a self-signed JWT naming a victim tenant/user; the forged identity then propagated to every consumer of the runtime context:OTel span attributes (sap.tenancy.tenant_id, user.id) via RuntimeContextSpanProcessorlog records via IdentityLogFilteraudit events (tenant_id, user_initiator_id) via AuditClienttenant routing via CBCClientThis completes an earlier remediation that fixed the same unverified pattern in StarletteIASTelemetryMiddleware but did not cover IASContextProvider.
CVE-2026-107245 is a stack-based buffer overflow vulnerability in the IPsec implementation of Versa VOS (Versa FlexVNF). It occurs when a maliciously crafted IKE Auth packet with an oversized Remote ID is sent to the WAN interface, causing the vsmd process to crash and resulting in a denial of service. This affects VOS nodes configured with certain IPsec VPN profiles using WAN interfaces as endpoints, including Controllers, Hub Controllers, and SSE Gateways. Nodes not accessible from the Internet are not vulnerable.
CVE-2026-107243 is a vulnerability in Versa VOS where the Node.js web service uses a hardcoded secret to sign session cookies. This secret is identical across all VOS appliances, allowing an attacker with a valid session ID to forge session cookies accepted by any appliance. The Node.js web service is intended only for initial Zero Touch Provisioning (ZTP) and should be disabled afterward to mitigate this risk.
MrDoc versions through 1.1.1 have a missing authorization vulnerability in the project_doc_sort and manage_project_doc_sort handlers. This flaw allows registered users to modify documents owned by other users by supplying arbitrary document IDs in sort_data. Attackers with access to any project can reorder and reparent documents by sequential ID and change their status to draft or removed, effectively hiding published documents.
A vulnerability in AMD Secure Encrypted Virtualization (SEV) firmware allows improper enforcement of behavioral workflow. This flaw could enable a malicious hypervisor to launch a guest with an attestation report containing an ID key digest that does not match the guest's measurement, resulting in loss of integrity.
INDOTALENT WHMS (Asp.Net-Core-Inventory-Order-Management-System) versions before 10.20261109 contain a critical authentication bypass vulnerability due to a hard-coded JWT signing key, issuer, and audience in the appsettings.json configuration file. This flaw allows unauthenticated remote attackers to forge tokens for any user ID and role trusted by the token validator, enabling them to gain administrator access to the entire API.
VanBlog versions up to 0.54.0 have an information disclosure vulnerability allowing unauthenticated attackers to access private and hidden articles. The flaw exists in the POST /api/public/article/:id endpoint, where private articles without effective passwords can be accessed by submitting any non-empty password. Additionally, hidden articles are exposed because the system does not properly check the hidden flag, allowing full content disclosure.
FileGator versions prior to 7.15.0 have a missing authorization vulnerability in the GET /batchdownload endpoint. This flaw allows a low-privileged user to download another user's batch archive by supplying its unique archive ID, bypassing the per-user home directory boundary in multi-user deployments. The archive ID is generated using a predictable uniqid() function without binding ownership metadata, enabling cross-user file disclosure. The vulnerability is limited to deployments with distinct per-user home directories and requires the attacker to have read, download, and batchdownload permissions. The issue is fixed in version 7.15.0.
An authenticated Pocket ID user can exploit a flaw where an email verification token remains valid after changing the account email address. The token is bound only to the user ID, not the email address, allowing the attacker to verify an email address they do not control. This leads to the system marking the new email as verified without proof of control. Consequently, relying parties that trust the verified email claim in OIDC can be tricked into linking the attacker's identity to a victim's account, enabling cross-application account takeover.
Wagtail versions prior to 7.0.9, 7.3.4, 7.4.3, and 8.0rc2 have a vulnerability where ETag conditional request processing occurs before permission and filename checks on the document serve endpoint. This allows an unauthenticated attacker who knows a document ID and a candidate SHA1 hash to determine if that hash exists in the document library by submitting If-Match or If-None-Match headers. The vulnerability does not expose document contents, filenames, or unknown hashes. The issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.
The Pocket ID client credentials grant implementation does not validate the requested resource parameter before embedding it as the audience (aud) claim in issued JWT access tokens. This allows any authenticated OIDC client to obtain tokens claiming authorization for arbitrary audiences, including other registered clients, without authorization checks. The introspection endpoint cannot detect misuse because it trusts the aud claim controlled by the requester. This vulnerability breaks audience-based access controls in deployments relying on Pocket ID for service-to-service authorization.
TrailBase versions from 0.28.2 up to but not including 0.35.10 contain an authorization bypass vulnerability in the FileUpload columns of the Record API. This flaw allows an authenticated attacker who can read a victim's row to recover the victim's file ID and subsequently delete or orphan the victim's file by manipulating records they own. The vulnerability is fixed in version 0.35.10.
Redpanda Connect versions 4.39 to 4.110 contain a missing authentication vulnerability that enables unauthenticated remote code execution (RCE). In streams mode, the management HTTP API is exposed on `0.0.0.0:4195`, but authentication is disabled by default and there is no authentication gate protecting the stream CRUD routes. An unauthenticated attacker with network access to TCP/4195 can `POST` a malicious pipeline definition to `/streams/{id}` that includes code-executing processors such as `command`, `subprocess`, `ffi`, or unsafe `sql_raw`, thereby achieving arbitrary RCE on the host with the permissions of the Redpanda Connect service account. Because pipelines can also return command output in-band via HTTP, this vulnerability enables full host compromise, credential theft, and data exfiltration with no user interaction or credentials required.
Starting with v4.111, the API endpoint was reconfigured as opt-in, so this and later versions are no longer vulnerable by default. However, RCE remains achievable on v4.111 and later if the management API is manually enabled via the `--bind-http` flag.
Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai allows a caller of an AshAi tool to read internal error details, including module names and data values, by making a tool call fail.
AshAi.ToToolError gained an implementation for Ash.Error.Unknown.UnknownError that returns the error's error field as is, and AshAi.Tool.Errors.format/1 sends that text to MCP clients (tool calls and resource reads in AshAi.Mcp.Server) and to the model in AshAi.ToolLoop. Ash stores the full Exception.format/2 output of a raised exception, or inspect/1 of a bare {:error, term} return, in that field. A tool result that cannot be JSON-encoded raises a Protocol.UndefinedError whose text includes the inspected value, which can be a whole record with fields the tool never returns. None of these errors were logged. The fix logs them under an error id and returns only that id to the caller.
This issue affects ash_ai: from 1.5.0 before 1.5.1.
Apache Airflow versions with multi-team deployments and secret cache enabled have a vulnerability where secret cache keys are constructed using unescaped underscore delimiters from team names and secret IDs. This can cause key collisions allowing a DAG author to access another team's Variable or Connection values. The issue affects deployments with both core.multi_team = True and secrets.use_cache = True. Upgrading to Apache Airflow 3.4.0 or later or disabling the secret cache mitigates the issue.
Apache Airflow versions with the non-default [core] test_connection setting enabled have a vulnerability where asynchronous connection tests improperly handle permissions. Specifically, users with create permission but without edit permission can overwrite existing connections if the test completes and commits the connection under an existing ID. This issue is fixed in Apache Airflow 3.4.0 and later.