Hashicorp
Monthly
A privilege escalation in KEDA 2.20.2 and earlier lets a namespace administrator who can create TriggerAuthentication and ScaledObject resources point hashiCorpVault.address at an endpoint they control and select Kubernetes authentication without supplying a credential; KEDA then logs in to that endpoint using the operator pod's projected ServiceAccount token, handing the attacker the operator's cluster-wide permissions including broad Secret reads and workload or admission-related operations. The prior CVE-2025-68476 JWT-shape filter does not block this path because the operator token's subject is a Kubernetes ServiceAccount, so it passes the filter. Exploitation is authenticated (CVSS PR:L) and gated by tenant-level RBAC to create those CRDs, but it is most dangerous in multi-tenant clusters where namespace admins are untrusted relative to the cluster-scoped operator; there is no public exploit code identified at time of analysis, and the issue is fixed in 2.21.0 via audience enforcement plus an outbound Vault-address allowlist.
Information exposure in the Dell Terraform Provider for OME, versions 1.0.0 through 1.2.3, occurs when the provider's API client error-handling path writes sensitive information into an externally accessible file or directory (CWE-209). Dell rates this CVSS 3.1 8.6 (High) with a remote, unauthenticated vector (AV:N/PR:N/UI:N/S:U/C:H/I:L/A:L), but independent assessment maps realistic exploitation to AV:L/AC:L/PR:N/UI:N/C:H/I:N/A:N, because an attacker must already be able to read wherever the provider's error output is persisted - typically shared log aggregation, publicly readable CI/CD output, or exposed Terraform state/debug artifacts - rather than reaching a directly network-exposed service. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor's AV:N vector should be validated against Dell DSA-2026-434 before treating this as a remotely exploitable unauthenticated issue.
Dell Terraform Provider for Redfish versions before 1.6.2 exposes Redfish BMC traffic, including credentials, to man-in-the-middle interception because TLS certificate verification is unconditionally disabled in its base HTTP transport. This critical-severity flaw (CVSS 9.0) allows an unauthenticated remote attacker who occupies a MITM position to capture or alter sensitive Redfish API communications, though exploitation is condition-gated to active provider-to-BMC traffic windows and is materially lower risk on trusted, isolated management segments. No public exploit identified at time of analysis; Dell recommends upgrading to 1.6.2.
Weak authentication handling in Microsoft's Azure Key Vault integration libraries allows unauthenticated remote attackers to bypass a security feature, with high confidentiality and integrity impact but no availability impact. The exposure is limited to applications and services that depend on specific vulnerable client SDK versions - the Python packages azure-keyvault-administration (<4.7.1), azure-keyvault-securitydomain (<1.0.0b3), and azure-keyvault-certificates/secrets/keys (<4.11.2), plus the .NET packages Azure.Security.KeyVault.Certificates/Secrets/Keys (<1.0.1); deployments already on patched versions are not exposed. Although the CVSS 3.1 vector (7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) indicates no authentication or user interaction is required, the High Attack Complexity reflects a meaningful non-trivial precondition - a timing or race window, a specific configuration, or an intermediary network position - rather than a single-request exploit of a default setup; no public exploit code has been identified at time of analysis, and this is a moderate-priority issue rather than an urgent fire drill.
Memory corruption in MongoDB libmongocrypt lets an authenticated actor who can modify key vault documents - or a malicious or compromised MongoDB server - crash or corrupt the memory of any client application that has Client-Side Field Level Encryption (CSFLE) or Queryable Encryption enabled. The trigger is a crafted key document containing duplicate masterKey fields, which causes provider-specific KMS data to be mis-typed during key-document cleanup, producing invalid memory access and invalid frees (CWE-843 type confusion). Scored 8.7 under CVSS 4.0, while our own assessment is more conservative at CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H, placing the confirmed impact at client-side crash and memory corruption rather than proven remote code execution; no public exploit code identified at time of analysis, and exploitation requires that encryption be in use plus key-vault write privileges (PR:L) or a hostile server.
Denial of service in MongoDB libmongocrypt occurs when KMS endpoint parsing triggers an integer underflow, causing an allocation failure that terminates the application process. This can be triggered by an authenticated user with write access to the key vault collection modifying a key document, or when an application passes a KMS endpoint containing a colon after its path or query during key creation. No public exploit code has been identified at time of analysis, and the vulnerability does not allow code execution, data disclosure, or data tampering-only a crash.
Privilege escalation in HashiCorp Vault and Vault Enterprise allows an authenticated principal with delegated permissions to bypass explicit deny ACL rules by referencing a resource or policy name in non-canonical form, potentially reaching a protected resource or assigning a denied policy. Affected are Vault Community Edition before 2.1.2 and Vault Enterprise before 2.1.2, 1.21.12, 1.20.17, and 1.19.23, rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires an already high-privileged, delegated user (PR:H) operating in a policy model that depends on explicit deny rules, and no public exploit code or confirmed active exploitation was identified at time of analysis (no EPSS data was provided), so this is best handled as a defense-in-depth hardening fix rather than an emergency.
Arbitrary code execution on the Vault host is achievable in HashiCorp Vault and Vault Enterprise when a privileged operator restores a crafted Integrated Storage (Raft) snapshot in a deployment configured with Shamir seals and an external plugin directory, because stored plugin catalog entries are not consistently verified to reference binaries inside that configured directory (CWE-22 path traversal). The attacker must already hold the high privileges needed to restore a Raft snapshot (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H), and exploitation also depends on the non-default Shamir-seal-plus-external-plugin-directory configuration, so this is a genuinely serious but condition-gated vulnerability rather than a mass-exploitation threat; clusters using auto-unseal or without an external plugin directory are not affected by this path. No public exploit identified at time of analysis, and vendor-released fixes are available in Vault Community Edition 2.1.2 and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.
Improper TLS certificate validation in the Confluent Kafka Python client's HashiCorp Vault KMS integration (confluent-kafka versions 0 through 2.14.2) allows a man-in-the-middle attacker to obtain sensitive information when the integration is used with its default configuration, which disables certificate verification. Successful exploitation requires the application to use the Vault KMS integration and the attacker to achieve a MITM position on the TLS connection to Vault, making this a conditional but significant risk (CVSS 7.4). No public exploit has been identified at the time of analysis.
Workload secrets are written to the initializer's standard output at INFO level in Edgeless Systems Contrast versions 1.9.0 through 1.12.1, so any Kubernetes principal that holds get or list permission on the pods/logs subresource in the affected namespace can read them from the container log stream. Because those workload secrets back Contrast's encrypted storage and HashiCorp Vault integration, the storage keys and Vault credentials derived from them must also be treated as compromised, giving the attacker a path to decrypt protected data and reach Vault-backed secrets. The flaw is a regression of GHSA-h5f8-crrq-4pw8 (originally fixed in 1.8.1 but never ported to the main branch), patchable in 1.12.2; there is no public exploit identified at time of analysis and no KEV listing, so risk is driven by the low barrier of an existing log-read RBAC grant rather than by active exploitation.
MCPVault, a lightweight Model Context Protocol server that exposes Obsidian vault files to AI agents, fails to block access to restricted directories such as .git, .obsidian, and node_modules in versions prior to 0.11.4. PathFilter compiles its deny-list patterns case-sensitively and matches raw path segments, so on case-insensitive macOS and Windows filesystems variants like .Git/config or .GIT/config (and on Windows, trailing-dot/space forms such as .git./config) pass both isAllowed() and isAllowedForListing() while the operating system still opens the real restricted directory. An attacker who can influence a path selected by an AI agent can then read, write, move, search, or list sensitive repository and Obsidian metadata; no public exploit code or CISA KEV entry was identified at time of analysis.
Vault secret values leak into error messages, log output, and Nomad task events in HashiCorp consul-template due to improper error handling. The vulnerability affects consul-template deployments integrated with HashiCorp Vault, where a template rendering error can inadvertently expose secret values to any downstream surface that receives error text - including Nomad task event logs readable by lower-privileged operators. The scope-changed CVSS vector (S:C) reflects that the primary harm falls on systems outside consul-template itself: Vault secrets meant to be accessed only by privileged services instead persist in Nomad task events and logging infrastructure accessible to broader audiences.
Authorization bypass in HashiCorp Consul's Connect service mesh allows a low-privileged authenticated service to communicate with destination services it is not authorized to reach. The flaw originates in Consul's Envoy RBAC rule generation: unescaped special characters in service names, namespaces, or partitions cause the generated matching rules to be overly permissive, defeating the Connect intentions authorization model. No public exploit or CISA KEV listing exists at time of analysis; fixes are available across Consul open-source and Enterprise release trains.
Authorization bypass in HashiCorp Consul's catalog node-write path allows any authenticated principal holding a node-write token-scoped to any node name whatsoever-to delete a different node's catalog registration and seize that node's identity within the service mesh. All Consul open-source and Enterprise versions prior to the fixed releases are affected, making shared or multi-tenant Consul clusters with delegated node-write tokens particularly exposed. No public exploit code or active exploitation has been identified at time of analysis, but the low access complexity and the typically discoverable nature of node IDs make this a credible lateral-movement and disruption vector in production service-mesh deployments.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Sensitive-file exposure in the openssl-encrypt pip package (openssl_encrypt) at versions <= 1.4.8 stems from its 'Encrypted USB Workspace' feature writing a marker that falsely declares the workspace AES-256-GCM encrypted while the derived key is never applied and the directory remains in cleartext. Users who trust the branding and store files in the workspace leave them fully readable on the removable media, so anyone with physical possession of the USB device can recover the data. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but the failure silently defeats the product's core security promise.
Path traversal in Atlantis workspace handling (versions 0.19.8 through 0.44.x) allows authenticated users to escape the intended workspace directory boundary, triggering os.RemoveAll and os.MkdirAll operations on arbitrary filesystem paths with Atlantis process privileges. A crafted workspace value such as '../../../../../../../../tmp/f1-canary' - supplied via repository atlantis.yaml or authenticated /api/plan API input - causes Atlantis to operate on out-of-bounds directories before Terraform rejects the invalid workspace name. A working proof-of-concept is documented in GHSA-26w5-6g95-gj28; the vulnerability is not in CISA KEV and no public exploit kit has been identified at time of analysis.
Improper TLS certificate validation in Splunk SOAR's CyberArk REST client exposes all credential vault traffic to interception and tampering by a network-positioned attacker. Versions below 8.6.0 are affected when a CyberArk REST credential manager integration is configured; the client accepts any server certificate without verification, making TLS sessions transparent to a man-in-the-middle. No public exploit code has been identified at time of analysis, and the vulnerability is absent from the CISA KEV catalog, but the high confidentiality and integrity impact on privileged credential data warrants priority remediation in environments relying on CyberArk for SOAR playbook secrets.
Server-side request forgery in the Red Hat Ansible Automation Platform 2 Controller's HashiCorp Vault credential plugin lets an authenticated user with credential-creation rights force the controller pod to leak its own Kubernetes service account token. When a HashiCorp Vault Secret Lookup credential configured for kubernetes_role authentication is tested, the kubernetes_auth() routine in awx_plugins/credentials/hashivault.py transmits the pod token to an attacker-supplied URL. With that token the attacker gains Kubernetes API access to control-plane namespaces, enabling full pod CRUD and secret reads including database credentials and the Django SECRET_KEY. No public exploit identified at time of analysis, and the flaw is not on the CISA KEV list.
Path traversal (CWE-22) in HashiCorp Packer's third-party plugin installer through version 1.15.4 permits a crafted plugin archive to write files outside the intended extraction directory, enabling code execution on the host. Users who install plugins from malicious or compromised sources trigger the vulnerability through the normal `packer plugins install` workflow. No public exploit code has been identified at time of analysis, and a vendor-released fix is available in Packer 1.16.0.
Arbitrary file read in HashiCorp Vault Secrets Operator versions 1.3.0 through 1.4.1 lets a low-privileged Kubernetes tenant abuse the AppRole authentication's SecretIDPath configuration to read files from the operator pod's filesystem and exfiltrate their contents to an attacker-controlled endpoint, enabling privilege escalation across the cluster. Because the operator pod typically holds credentials and tokens spanning multiple tenants, a single limited-RBAC tenant can cross trust boundaries (CVSS scope change), yielding a 9.6 rating. No public exploit identified at time of analysis, but the low attack complexity and multi-tenant blast radius make this a high-priority patch.
Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.
Unauthenticated denial of service in HashiCorp Consul's external gRPC listeners allows remote attackers to exhaust agent file descriptors, goroutines, and memory by flooding incomplete connections, rendering the agent unreachable to legitimate clients. Both Consul Community Edition and Consul Enterprise versions 1.13.0 through 2.0.2 are affected - a span covering nearly three years of releases. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 7.5 score and AV:N/AC:L/PR:N profile reflect a straightforwardly exploitable network condition requiring no attacker authentication or user interaction.
Command injection in sysPass's backup service allows any authenticated administrator to execute arbitrary OS commands as the web server process user by storing shell metacharacters in the backup path configuration setting and triggering a backup operation. Because sysPass is a self-hosted password manager, successful exploitation grants direct read access to the master encryption key and entire credential vault, enabling mass credential disclosure and lateral movement to every system whose passwords are stored in sysPass. A public proof-of-concept is available via the referenced gist (https://gist.github.com/W40X/6747ba1b7da7bb69b0c0e162628df279); no CISA KEV listing was identified at time of analysis.
Cross-namespace traffic hijacking in Traefik's Kubernetes Gateway API provider allows a low-privileged tenant to redirect another namespace's HTTP, GRPC, TCP, or TLS traffic to an attacker-controlled backend. The root cause is a non-injective route identity scheme: namespaces and route names are hyphen-concatenated without field delimiters, so namespace=team/route=a-app and namespace=team-a/route=app produce the identical key httproute-team-a-app-..., and the later-loaded route silently overwrites the earlier one via maps.Copy. No public exploit identified at time of analysis as a KEV entry, but a full proof-of-concept bash script is publicly available and was verified against the official traefik:v3.7.8 image. All Traefik v3 releases prior to v3.6.25 and v3.7.10 are affected.
Missing admin authorization on the embedding management API in Odysseus allows any authenticated non-admin user to overwrite or delete the server-wide embedding backend configuration, redirecting all subsequent embedding operations - including chat messages, RAG queries, memory entries, and vault text - in plaintext to an attacker-controlled URL. All deployments running any version prior to commit bf325f6 are affected. A public exploit and detailed write-up are available, and the CVSS 4.0 score of 8.7 (PR:L) reflects the low barrier to exploitation for any account holder.
Server-side request forgery in bank-vaults vault-secrets-webhook (<= 1.22.2) lets a low-privileged tenant with ConfigMap or Secret create/update rights in any watched namespace force the cluster-wide admission webhook to make attacker-controlled outbound HTTP requests and exfiltrate ServiceAccount JWTs. The webhook trusts the vault.security.banzaicloud.io/vault-addr annotation with no scheme validation or host allowlist, then synchronously mints a SA token (via cluster-wide serviceaccounts/token:create) and POSTs it to the attacker's address, which can be replayed against the real Vault. A vendor patch (v1.23.1) exists and the reporter published a working PoC, but there is no public exploit identified in the wild and the flaw is not in CISA KEV.
Path traversal and query parameter injection in hashi-vault-js (npm, versions ≤ 0.5.1) allow an attacker who can influence identifiers passed to the library to redirect Vault API requests to arbitrary endpoints - including administrative paths such as `/v1/sys/seal` - or inject unauthorized query parameters, all executed under the permissions of the application's configured Vault token. The vulnerability arises because `Vault.js` contains zero calls to `encodeURIComponent()`, concatenating every caller-supplied identifier directly into HTTP URL strings. Two attack vectors are dynamically confirmed in the GHSA advisory: path traversal via `../../sys/seal` as a secret name, and query injection via `1&list=true` as a version value. No public standalone exploit tool has been identified and this CVE is not listed in the CISA KEV catalog.
Cross-session token leakage in HashiCorp consul-mcp-server 0.1.0 through 0.1.3 allows one client's Consul authentication token to bleed into requests issued by other clients when the server runs in stateless mode, effectively enabling an attacker to act against Consul with a victim's credentials. HashiCorp rated this CVSS 10.0 (scope-changed) because the borrowed token grants the attacker the victim's full Consul read/write authority across a trust boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; the fix is consul-mcp-server 0.1.4.
Server-Side Request Forgery in HashiCorp's consul-mcp-server 0.1.0 through 0.1.3 lets a connected client override the server's configured Consul backend address through an untrusted request header, redirecting the server's Consul API calls to an attacker-controlled endpoint and exfiltrating the privileged Consul token held by the server. The flaw carries a CVSS 8.6 (scope-changed, high confidentiality impact) and is fixed in 0.1.4; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Credential reuse in Terraform MCP Server allows cross-tenant token leakage, enabling unauthorized tool execution on behalf of other users. The vulnerability affects versions prior to 1.1.0 when the server is run in streamable-HTTP stateless transport mode. No public exploit code is known, but the critical CVSS score and network attack vector indicate high potential risk.
Authorization bypass in HashiCorp's terraform-mcp-server (versions 0.3.0 through 1.0.x) lets an attacker who obtains another user's MCP session identifier execute their own tool calls under the victim's Terraform credentials when the server runs in streamable-HTTP stateful transport mode. Rooted in a session fixation weakness (CWE-384), the flaw carries a CVSS 8.9 with a scope change, meaning cross-user credential misuse against managed infrastructure. No public exploit identified at time of analysis; EPSS is low (0.27%) and CISA SSVC records exploitation as none, indicating no observed active exploitation.
Server-side request forgery in HashiCorp terraform-mcp-server before 1.1.0 allows unauthenticated remote attackers to redirect Terraform API requests and steal server-side authorization tokens via the streamable-HTTP transport. The vulnerability, tracked as CVE-2026-14869, permits an attacker to control the destination of outbound requests, leading to token exposure. No public exploit or active exploitation has been reported at this time.
Privilege escalation in sysPass 3.2.11 allows authenticated users with the PUBLICLINK_CREATE profile flag to decrypt passwords of arbitrary vault accounts and store them in public links, enabling unauthenticated retrieval if the link hash is obtained. No active exploitation is confirmed, but public exploit code exists; EPSS probability is low (0.18%).
Missing object-level authorization in sysPass through 3.2.11 allows API token holders to enumerate account metadata, overwrite passwords, and delete any account across the vault without per-account access controls. A public proof-of-concept is available, though EPSS indicates low exploitation probability (0.22%).
Authenticated attackers can bypass access controls in sysPass 3.2.11 and earlier to access, download, or delete any account file attachment, regardless of their ACL permissions, by exploiting missing authorization checks in AccountFileController. Public exploit code is available, but the EPSS score of 0.22% indicates low likelihood of widespread exploitation.
Authentication bypass in Microsoft Azure Key Vault lets a remote, unauthenticated attacker elevate privileges over the network and gain unauthorized access to the secrets, keys, and certificates the service protects. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) rates it 9.8 Critical with full confidentiality, integrity, and availability impact. A vendor patch is available; there is no public exploit identified at time of analysis, and EPSS exploitation probability is low (0.70%, 49th percentile) despite CISA SSVC flagging the flaw as automatable with total technical impact.
Server-side request forgery and internal repository exfiltration in Gitea before 1.27.0 lets a low-privileged authenticated user bypass the migration URL allow/block list by supplying a permitted public Git URL that HTTP-redirects the server's git subprocess to an otherwise-blocked internal endpoint. Because Gitea validates only the originally submitted URL while git runs with its default http.followRedirects=initial, the redirected internal Git repository is cloned into an attacker-controlled repository, and pull mirrors keep re-fetching it on schedule. No public exploit identified at time of analysis; a vendor-authored local proof-of-concept confirmed the redirect is followed to 127.0.0.1, and EPSS/KEV data were not supplied.
Local File Read in Anyquery's Server Mode lets unauthenticated network attackers exfiltrate arbitrary files (e.g. /etc/passwd, ~/.ssh/id_rsa) readable by the server process. When `anyquery server` is running and reachable, any client speaking the MySQL wire protocol can issue native SQLite CREATE VIRTUAL TABLE statements against built-in reader modules such as csv_reader or log_reader to point at restricted paths, with no authentication or credentials required (CVSS 3.1 base 7.5, C:H/I:N/A:N). A working proof-of-concept is published in the GHSA advisory, so publicly available exploit code exists; there is no CISA KEV listing or EPSS score in the provided data.
Authorization bypass in Sonatype Nexus Repository 3's component upload API lets an account holding only read/browse privileges on a Swift, Terraform, or Conda hosted repository push arbitrary artifacts, defeating the intended write-permission check (CWE-862). The flaw affects the specific upload paths for these three formats and enables unauthorized artifact publishing that can poison downstream builds. No public exploit identified at time of analysis; Sonatype has shipped a fix in release 3.94.0.
Server-side request forgery in the Ruby css_parser gem (< 3.0.0) lets a remote unauthenticated attacker force the parsing server to issue arbitrary HTTP/HTTPS GET requests, and via an attacker-controlled 3xx redirect to a file:// URI, escalate to arbitrary local file disclosure. The flaw sits in CssParser::Parser#read_remote_file, reachable through load_uri! and any add_block! call that supplies base_uri: - Premailer being the canonical consumer - so a single attacker-planted @import url(...) in parsed CSS reaches the sink. Publicly available exploit code exists (author-supplied PoC); there is no public exploit identified as being used in active campaigns, and it is not listed in CISA KEV.
Container-to-host sandbox escape in HashiCorp Nomad and Nomad Enterprise lets an authenticated job submitter using the Docker task driver bind-mount an arbitrary host path into their container even when volume bind mounts are administratively disabled, enabling read and write access to files on the underlying host. The scope-changing flaw (CVSS 3.1 8.7) affects the Community and Enterprise editions and is fixed in Nomad 2.0.4 (CE), and Enterprise 2.0.4, 1.11.8, and 1.10.14. There is no public exploit identified at time of analysis and it is not on CISA KEV.
Account takeover in self-hosted Bitwarden Server before 2026.6.0 lets a low-privileged organization member steal any other member's vault key and a victim-scoped access token. The POST /auth-requests/admin-request handler never verifies that the email in the request body belongs to the authenticated caller (CWE-639), so an attacker can create a Trusted Device Encryption admin-approval request for a victim, bound to an attacker-controlled public key; once approved, the encrypted key material is retrievable from an unauthenticated endpoint. Publicly available exploit code exists (a VulnCheck advisory plus a public write-up), and the CVSS 4.0 base score of 9.3 reflects high confidentiality and integrity impact plus a cross-user scope change.
Host namespace escape in HashiCorp Nomad and Nomad Enterprise lets an authenticated job submitter bypass the allow_privileged control for the Docker task driver, launching containers in host PID/network/IPC namespaces to read data from the host or co-located workloads on the same client node. The flaw stems from missing authorization enforcement (CWE-862) and carries a CVSS 7.7 with a changed scope, reflecting cross-tenant impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
SQL and DDL injection in the Snowflake Terraform Provider before 2.18.0 lets an attacker who can influence pipeline workspace variables execute arbitrary SQL inside the provider's privileged Snowflake session (CWE-89), enabling data exfiltration and creation of long-lived credentials. A second flaw allows identifier-injection into user-management DDL, so accounts can be minted with attacker-controlled credentials that bypass operator-configured security controls. No public exploit identified at time of analysis; risk is authenticated/insider-driven rather than remote-unauthenticated.
Arbitrary file read in HashiCorp Terraform Enterprise allows an authenticated user to escape the intended repository boundary during VCS-based registry module ingestion, pulling files from outside the source repository into a packaged module and downloading them. Because the ingestion process runs with its own filesystem privileges, an attacker can exfiltrate sensitive files (secrets, configuration, tokens) readable by that process. Reported by HashiCorp with no public exploit identified at time of analysis; the CVSS 7.7 (scope-changed) score reflects high confidentiality impact against a self-hosted enterprise platform.
Java object deserialization in the Apache Camel camel-pqc component allows code execution in the key-management application when an attacker who can write to the backing AWS Secrets Manager secret stores a malicious serialized payload. The flaw affects Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x, where AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() calls a raw ObjectInputStream.readObject() with no class filter, so gadget side effects fire before the KeyMetadata cast. Rated CVSS 9.8 by Apache, but exploitation genuinely requires IAM write access to the specific secret; there is no public exploit identified at time of analysis and EPSS is low at 0.19% (8th percentile).
Remote code execution via unsafe Java deserialization affects the camel-pqc component of Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x. The HashiCorp Vault and AWS Secrets Manager KeyLifecycleManager implementations (and a legacy-migration path in the file-based manager) read post-quantum key metadata back with a raw ObjectInputStream.readObject() lacking any ObjectInputFilter or allow-list, so a principal able to write to the key backend can plant a gadget object that executes during normal key-lifecycle operations. No public exploit has been identified at time of analysis and EPSS is low (0.19%), but SSVC rates technical impact as total; this is an incomplete-remediation follow-on to CVE-2026-40048.
Server-side request forgery and secret disclosure in the Apache Camel camel-iggy consumer (versions 4.17.0-4.18.2 and 4.19.0-4.20.x) allow an actor able to publish to a consumed Iggy stream to inject Camel control headers such as CamelHttpUri into the Exchange. When the consumer feeds a downstream HTTP producer, the attacker redirects the server-side request to internal services or cloud metadata endpoints, and because the producer resolves Camel property placeholders on the attacker-controlled URI, environment variables, application properties, and vault secrets are exfiltrated. No public exploit identified at time of analysis, and EPSS is low (0.15%), but the confidentiality impact is rated High.
Server-side request forgery and secret disclosure in Apache Camel's camel-atmosphere-websocket component allow a remote attacker to hijack downstream server-side HTTP requests by injecting Camel control headers as WebSocket query parameters. Affecting Camel 4.0.0-4.14.7, 4.15.0-4.18.2 and 4.19.0-4.20.x, the flaw lets an attacker set CamelHttpUri to redirect internal HTTP calls (e.g., to cloud metadata endpoints) and force resolution of Camel property placeholders, leaking environment variables, application properties and vault secrets. Where the WebSocket endpoint is exposed without authentication the issue is unauthenticated (CVSS 7.5); there is no public exploit identified at time of analysis and EPSS is low (0.24%).
Server-side request forgery and secret disclosure in Apache Camel's camel-vertx-websocket component (versions 4.0.0-4.14.7, 4.15.0-4.18.2, and 4.19.0-4.20.x) let a WebSocket client inject Camel-internal control headers such as CamelHttpUri because inbound query/path parameters are copied into the Exchange header map without a HeaderFilterStrategy. In routes that bridge the WebSocket consumer into a downstream HTTP producer, an attacker can redirect the server-side HTTP request to internal services or cloud metadata endpoints, and because the HTTP producer resolves Camel property placeholders on the attacker-supplied URI, environment variables, application properties, and vault secrets are resolved and exfiltrated. When the WebSocket endpoint is exposed without authentication (PR:N per CVSS), this is reachable by an unauthenticated remote attacker; there is no public exploit identified at time of analysis, and EPSS is low at 0.24%.
Credential disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows any authenticated user to retrieve plaintext OAuth tokens, vault passwords, and SSH keys by sending forged Worker messages to the Event-Driven Ansible websocket endpoint. The /api/eda/ws/ansible-rulebook endpoint fails to verify permissions on activation_id values, enabling lateral credential theft across tenants. No public exploit identified at time of analysis, but the low attack complexity and scope-changed CVSS of 9.6 make this a high-priority patch.
Denial of service in CyberArk Privileged Access Manager (PAM) Self-Hosted Vault allows remote attackers to terminate the Vault service by sending unexpected input under specific configuration scenarios, affecting versions prior to 15.0.3, 14.6.5, 14.2.7, and 14.0.8. Disclosed by Palo Alto Networks (which now owns CyberArk) via Security Bulletin CA26-17 with no public exploit identified at time of analysis, the CVSS 4.0 base score of 8.7 reflects the network-reachable, unauthenticated attack path against a security-critical service. The flaw is a CWE-400 resource/input handling issue that produces a localized DoS rather than code execution or data exposure.
Arbitrary file write in the Altium Enterprise Server Vault Service allows authenticated users to escape the configured storage root via the UploadController image upload endpoint and place content-controlled files anywhere the service account can write. The flaw (CVSS 4.0 base 9.4, CWE-22) escalates to remote code execution, service takeover, or denial of service by overwriting application binaries, configuration files, or dropping payloads in web-accessible directories. No public exploit identified at time of analysis, and Altium 365 cloud deployments are explicitly out of scope.
Unauthenticated file disclosure and arbitrary file read in Altium Enterprise Server prior to 8.1.1 allows any network-reachable attacker to forge signed Vault download URLs using a hard-coded key shipped identically across all installations. Chained with a co-located path traversal in the same download endpoint (and optionally CVE-2026-9152 for enumeration), an attacker can read arbitrary server-side files including configuration and key material, leading to full server compromise. No public exploit identified at time of analysis; CVSS 4.0 score is 10.0 and Altium 365 SaaS is not affected because cloud deployments use object storage rather than the local filesystem.
Missing authentication in the Altium 365 SearchService lets an unauthenticated network attacker who knows a target workspace identifier interact with that workspace's search index across tenant boundaries via a legacy SOAP endpoint. Affecting Altium 365 cloud deployments (on-premise Altium Enterprise Server is not affected), it enables reading indexed component, project, folder, and user metadata and injecting, modifying, or deleting search index entries - an authentication bypass with no public exploit identified at time of analysis, though CISA's SSVC framework marks the flaw automatable with total technical impact.
Supply-chain compromise of the npm package @beproduct/nestjs-auth (versions 0.1.2 through 0.1.19) delivered the Mini Shai-Hulud worm payload via a malicious postinstall script, harvesting npm, GitHub, AWS, and HashiCorp Vault credentials from any developer or CI host that ran npm install during a 2h37m publication window on 2026-05-11. Confirmed actively exploited during that window via an attacker-controlled npm publish token; clean version 0.1.20 republishes the original 0.1.1 source tree. CVSS 10.0 reflects the unauthenticated, network-driven supply-chain delivery and scope change into the install environment.
Unauthenticated agent token theft in Coder v2 (self-hosted developer workspace platform) stems from azureidentity.Validate() verifying the PKCS#7 signer's certificate chain but skipping signature verification of the signed content itself. Remote attackers who know a target VM's vmId (a UUIDv4) can forge a PKCS#7 envelope containing a legitimate Azure certificate alongside attacker-controlled content and POST it to the unauthenticated /api/v2/workspaceagents/azure-instance-identity endpoint to receive the victim workspace agent's session token, which then unlocks Git SSH keys, OAuth tokens for GitHub/GitLab/Bitbucket, and workspace secrets. No public exploit identified at time of analysis, but the vulnerability is vendor-confirmed via GHSA-6x44-w3xg-hqqf and a detailed root-cause analysis with attack-path diagram is published.
Server-Side Request Forgery in Tenable Terrascan v1.18.3 and prior allows unauthenticated remote attackers to coerce the server into fetching arbitrary URLs, including file:// URIs that enable local file disclosure. The flaw is triggered when Terrascan runs in server mode and parses uploaded ARM or CloudFormation templates whose templateLink.uri, parametersLink.uri, or AWS::CloudFormation::Stack TemplateURL fields point to attacker-controlled destinations. No public exploit identified at time of analysis, and because Terrascan was archived in August 2023, no patch will ever be released.
Server-Side Request Forgery in Tenable's Terrascan IaC scanner (versions 1.18.3 and prior) lets unauthenticated remote attackers read arbitrary local files and exfiltrate ~/.netrc credentials when the tool runs in server mode. Because Terrascan was archived in August 2023, no vendor patch will ever be released, and the daemon binds to 0.0.0.0 with no authentication by default. No public exploit identified at time of analysis, but the CVSS 4.0 score of 9.2 reflects trivial network-reachable abuse paired with significant confidentiality scope change.
Authenticated code execution on Nomad client hosts is possible in HashiCorp Nomad and Nomad Enterprise 1.10.0 through versions prior to 2.0.1 via a path traversal flaw in the dynamic host volume feature. A submitter with volume-creation privileges can escape the intended volume directory and write to or execute code in arbitrary locations on the client node's filesystem, gaining code execution outside the intended sandbox. This flaw is not in CISA KEV and has no public exploit identified at time of analysis; EPSS probability is low at 0.03%.
Full administrative database takeover in Google Cloud AlloyDB for PostgreSQL affected clusters provisioned via Terraform or the REST API before 2025-11-03, where those provisioning paths applied an insecure default password. A remote attacker with network reachability to such a cluster could authenticate as a privileged account and gain complete control of the database. There is no public exploit identified at time of analysis, and the EPSS probability is very low (0.04%, 12th percentile), consistent with the SSVC assessment of no observed exploitation.
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actions exploitation. Attackers combined pull_request_target misconfiguration, Actions cache poisoning, and OIDC token memory extraction to publish malicious code under the legitimate TanStack identity. Installing any affected version executes a 2.3 MB obfuscated payload that exfiltrates AWS/GCP/Kubernetes credentials, npm tokens, GitHub secrets, SSH keys, and HashiCorp Vault tokens over encrypted Session/Oxen messenger infrastructure. The payload propagates by republishing victim-maintained packages with identical injection. Socket.dev and the TanStack team confirmed the incident via GHSA-g7cv-rxg3-hmpx. No EPSS or CISA KEV data available for this recent supply-chain attack. CVSS 9.6 reflects the cross-scope credential theft impact (S:C/C:H/I:H), though exploitation requires user-initiated package installation (UI:R).
Improper authorization in Vaultwarden (self-hosted Bitwarden-compatible server) before 1.35.5 lets an authenticated user who was invited as an organization owner and has accepted-but not yet been confirmed-invoke POST /api/ciphers/purge to hard-delete every cipher and attachment in the organization. The endpoint checks only that membership type is Owner and omits the required Confirmed-status check, enabling irreversible organization-wide data loss. There is no public exploit identified at time of analysis, EPSS is negligible (0.04%), and SSVC records no known exploitation.
Cross-organization authorization bypass in Vaultwarden (the Rust-based, self-hosted Bitwarden-compatible server) prior to 1.35.5 lets an attacker who holds Admin rights in one organization pivot into a second organization where they are only a low-privileged member. Because group-management endpoints persist arbitrary MembershipId and CollectionId values without checking org consistency (CWE-285), the attacker can bind their foreign Org B membership into an accessAll Org A group and read - then write - Org B vault data via /api/sync and /api/ciphers. A POC is referenced in the SSVC data (publicly available exploit code exists); it is not in CISA KEV and EPSS is very low (0.03%), consistent with a targeted, multi-step abuse rather than mass exploitation.
Authentication bypass in UltraDAG Core blockchain allows remote unauthenticated attackers to drain all pocket-derived sub-addresses on smart accounts, completely bypassing vault delays and daily spending limits. The StateEngine fails to resolve pocket addresses to their parent account during policy enforcement, treating virtual pocket addresses as unrestricted accounts. Confirmed actively exploited (CISA KEV). Vendor-released patch: commit fb6ef59 resolves pocket-to-parent mapping before all policy checks. EPSS data unavailable but attack vector is network-accessible with no complexity (CVSS 4.0 AV:N/AC:L/PR:N), making this a critical priority for any UltraDAG deployment using smart account pockets.
Server-side authentication bypass in the OpenTelemetry Collector Contrib azureauthextension (v0.124.0-v0.150.0) lets any holder of a valid Azure access token minted for the collector's service principal authenticate to any receiver configured with auth: azure_auth. The extension never validates bearer tokens as JWTs; it mints its own token using the client-supplied Host header as the scope and compares strings, so a token issued for an unrelated Azure resource (ARM, Graph, Key Vault, Storage) is accepted if the attacker sets a matching Host. No CISA KEV listing and EPSS is very low (0.05%), but the vendor advisory (GHSA-pjv4-3c63-699f) documents a working proof-of-concept for both replay and scope-confusion variants.
Network-accessible denial-of-service in HashiCorp Boundary workers allows unauthenticated remote attackers to block legitimate worker connections by manipulating TLS handshake timing during node enrollment. Attackers can connect to the worker authentication listener and intentionally delay or withhold client certificates, causing connection handlers to block and preventing legitimate workers from enrolling or routing traffic. Both Community Edition and Enterprise versions prior to 0.21.3, 0.20.3, and 0.19.5 are vulnerable. EPSS data not provided; no CISA KEV listing indicating limited observed exploitation. Vendor-confirmed vulnerability with patches released across three active release branches.
HashiCorp Vault unauthenticated denial-of-service vulnerability allows remote attackers to block critical administrative operations by monopolizing the single operation slot for root token generation and rekey workflows. Affects all Vault Community and Enterprise versions prior to 2.0.0. No active exploitation confirmed (EPSS 3rd percentile), but attack is trivially automatable per CISA SSVC framework. HashiCorp released patches in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.
Token leakage in HashiCorp Vault and Vault Enterprise (0.11.2 up to 2.0.0, 1.21.5, 1.20.10, and 1.19.16) occurs when an auth mount is configured to pass through the 'Authorization' header and that same header is used to authenticate to Vault; in this case Vault forwards the caller's Vault token onward to the auth plugin backend. An authenticated client's token is thereby exposed to a plugin backend that should never see it, enabling potential impersonation and unauthorized secret access. No public exploit identified at time of analysis, and EPSS exploitation probability is negligible (0.01%, 3rd percentile).
HashiCorp Vault's KVv2 secrets engine allows authenticated users with glob-based policy access to delete secrets outside their authorization scope, causing denial-of-service across versions 0.10.0 through 1.x. The flaw stems from improper access control (CWE-288) in policy glob evaluation during delete operations. Exploitation requires valid Vault credentials with specific policy patterns but does not permit cross-namespace deletion or secret data exfiltration. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0/1.21.5/1.20.10/1.19.16. No active exploitation confirmed (EPSS 0.01%), but CVSS 8.1 reflects high integrity and availability impact for authenticated attackers.
Arbitrary file read vulnerability in HashiCorp go-getter library versions up to 1.8.5 enables unauthenticated remote attackers to access sensitive files from the target filesystem through specially crafted git operation URLs. The vulnerability permits confidentiality breach without authentication requirements, affecting network-accessible services utilizing the library for repository cloning or fetching operations. Fixed in version 1.8.6; go-getter/v2 branch unaffected. No public exploit identified at time of analysis.
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks against Dgraph graph database servers (v24.x, v25.x prior to v25.3.1) via the admin API's restoreTenant mutation. The mutation bypasses all authentication middleware due to missing authorization configuration, allowing attackers to provide arbitrary backup source URLs (including file:// schemes for local filesystem access), S3/MinIO credentials, Vault configuration paths, and encry
Authenticated users in n8n versions prior to 1.123.23 and 2.6.4 can bypass external secrets permission checks to retrieve plaintext secret values from configured vaults by referencing secrets by name in credentials, even without list permissions. This allows unauthorized access to sensitive vault-stored credentials without requiring admin or owner privileges, provided the attacker knows or can guess the target secret name. Public exploit code exists for this vulnerability.
An integrity check vulnerability in Cryptomator for Android prior to version 1.12.3 allows attackers to tamper with the vault configuration file, enabling a man-in-the-middle attack against the Hub key loading mechanism. Attackers who can modify the vault.cryptomator file can mix legitimate authentication endpoints with malicious API endpoints to exfiltrate tokens from users unlocking Hub-backed vaults. With a CVSS score of 7.6 and requiring low attack complexity with user interaction, this vulnerability poses a moderate risk to affected users in environments where vault configuration files can be altered.
A man-in-the-middle vulnerability in Cryptomator for iOS versions prior to 2.8.3 allows attackers who can modify the vault.cryptomator configuration file to intercept authentication tokens by substituting malicious API endpoints while maintaining legitimate authentication endpoints. This affects users unlocking Hub-backed vaults in environments where attackers have write access to vault configuration files. No evidence of active exploitation (not in CISA KEV) has been reported, and patches are available.
Cryptomator's Hub-based unlock flow contains a protocol downgrade vulnerability that allows the application to communicate with Hub endpoints over plaintext HTTP instead of enforcing HTTPS. Cryptomator versions prior to 1.19.1 are affected, exposing OAuth bearer tokens, key-loading traffic, and endpoint-level trust decisions to network interception and tampering by active attackers. This is a verified GitHub security advisory with patches available in version 1.19.1, though no EPSS score or KEV listing indicates limited evidence of active exploitation.
Cryptomator versions prior to 1.19.1 contain an integrity check vulnerability that allows attackers to tamper with the vault.cryptomator configuration file, enabling man-in-the-middle attacks during Hub key loading. Attackers can mix legitimate authentication endpoints with malicious API endpoints to exfiltrate access tokens from users unlocking Hub-backed vaults in environments where vault configuration files can be modified. The CVSS score of 7.6 indicates high severity with network attack vector requiring low privileges and user interaction, though no active exploitation (KEV) or public POC has been reported at this time.
An authorization bypass vulnerability exists in the Vault secrets back-end implementation of Canonical's Juju orchestration tool, allowing authenticated unit agents to perform unauthorized updates to secret revisions beyond their intended scope. Juju versions 3.1.6 through 3.6.18 are affected, and attackers with sufficient information can poison any existing secret revision within the Vault secret back-end scope. With a CVSS score of 7.6 (High severity) featuring network attack vector, low complexity, and high integrity impact, this represents a significant security concern for Juju deployments using Vault as their secrets back-end, though no active exploitation (KEV) status or EPSS score was provided in available data.
Insecure password saving enforcement in Devolutions Remote Desktop Manager 2025.3.
Dell Terraform Provider for OME versions 1.0.0 through 1.2.3 inserts sensitive provider configuration data into log files, so an authenticated, low-privileged remote attacker who can read those logs may obtain limited confidential information about the managed environment. Scored 4.3 (Medium) as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, the issue requires prior low-level access plus reachability of the log destination, with no integrity or availability impact. No public exploit code has been identified at time of analysis, and no confirmed active exploitation is reported, so practical risk is governed by what the provider actually writes to logs and how tightly log retention and access are controlled.
Sensitive information handled by the redfish_certificate resource in the Dell Terraform Provider for Redfish (versions 1.1.0 through 1.6.1) can be exposed to unauthorized parties through CWE-532 weakness, most plausibly via Terraform debug logs, state files, or CI/CD console output. Exploitation requires a high-privileged actor operating within the Terraform workflow (PR:H) who also has access to wherever the sensitive data is written, so realistic abuse is confined to users already close to the automation pipeline; the bounded version range and low confidentiality impact further constrain it. The vendor scores this CVSS 4.3, and our independent assessment concurs at 4.3 with confidentiality-only impact, making it a low-severity information-exposure issue rather than an urgent patching priority. No public exploit identified at time of analysis.
Path traversal in HashiCorp go-getter's S3 and GCS directory-download handling lets files be written outside the requested destination, affecting go-getter before 1.8.10 and go-getter/v2 before 2.2.5. Unauthenticated remote attackers (CVSS PR:N) can only succeed if a victim initiates a download against an attacker-influenced S3 or GCS bucket that contains crafted object keys with traversal sequences, which is why the vector requires user interaction (UI:R) and carries high attack complexity (AC:H); the resulting impact is integrity-only (CVSS 5.3, I:H with no confidentiality or availability effect). No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor patches are available.
Cross-namespace privilege escalation in HashiCorp Vault Enterprise allows an authenticated token holding a specially crafted policy name containing path-traversal constructs to have its policy resolved against a different namespace - including the root namespace - thereby gaining capabilities granted by policies it should never reach. Only Vault Enterprise deployments with namespaces actually configured are exposed; Vault Community Edition does not implement namespaces and is explicitly not affected. Exploitation requires a valid token (CVSS PR:L, authenticated) and the resulting privilege gain is bounded by whatever policies exist in the traversed namespace, making this a moderate-priority privilege-escalation issue rather than a mass-exploitation threat - no public exploit code has been identified at time of analysis and no EPSS or KEV data was supplied.
HashiCorp Vault's PKI secrets engine ACME server, when running under the default directory policy, can issue certificates that contain identity claims the ACME challenges never validated, allowing an unauthenticated ACME client (CVSS vector PR:N/UI:N) to obtain a certificate for an identity it does not control and impersonate that identity toward systems that trust the affected Vault PKI mount. The issue is a configuration-dependent certificate-integrity flaw (CVSS 5.9, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) rather than an urgent remote-code or data-exposure bug: it requires a PKI mount with the ACME server enabled under the default directory policy and relying systems that actually trust certificates issued by that mount, otherwise the unverified identity has no effect. HashiCorp addressed it in Vault Community Edition 2.1.2 and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23; no public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied in the available data.
Trivy versions before 0.71.0 allow directory traversal through Terraform filesystem functions during misconfiguration scanning of untrusted input, potentially exposing sensitive files located outside the scan root. An attacker able to supply a malicious Terraform configuration (e.g., via a third-party pull request) can use relative paths like '../secret' in file() or filebase64() to include the contents of files above the scan directory in scan output. Exploitation requires the sensitive file to exist at a guessable traversal path and is confined to information disclosure (C:L) with high attack complexity; no public exploit has been identified at time of analysis.
Cross-team secret disclosure in the HashiCorp Vault secrets backend for Apache Airflow lets an authenticated Dag author scoped to one team read Vault secrets belonging to a different team in multi-team deployments. The flaw (CWE-639, authorization bypass through a user-controlled key) triggers when the team-scoped lookup misses and the backend falls back to a team-agnostic path concatenated from the unvalidated Variable key; because the Execution API Variables route accepts a path-shaped key, the traversal is reachable from ordinary Dag code. The vendor assigned no CVSS score (CVSS: N/A), while the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - read-only disclosure with scope change and no integrity or availability impact; single-team deployments are unaffected, no public exploit code has been identified at time of analysis, and the vendor-released fix is apache-airflow-providers-hashicorp 4.8.0.
Ansible Automation Platform 2's gateway permits an authenticated gateway administrator (CVSS PR:H) to create a new service key for the Controller service cluster through the API, even though service-key creation is supposed to occur only via the installer-provisioned path; the resulting key is cryptographically indistinguishable from a legitimate one, so it can be used to mint a service-authentication token that impersonates the Controller service. When the non-default gateway OIDC workload-identity endpoint is enabled (FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED) and a downstream resource server such as HashiCorp Vault trusts the gateway's OIDC signing key, the attacker can induce the gateway to sign Workload Identity Tokens for arbitrary Controller workloads and retrieve the AAP credentials bound to that workload, crossing the administrator's authorization boundary to disclose secrets (C:H, no integrity or availability impact). Exploitation requires admin privileges plus that specific non-default trust configuration, and no public exploit has been identified at time of analysis; the defect is access-gated rather than broadly exploitable.
Improper validation of parameters in GitLab CE/EE's Terraform state upload functionality allows an authenticated user holding project-level permissions to read restricted file contents on the server or cause denial of service. Affected releases are all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with fixes published in the 19.3.2 patch release. Public exploit details exist via a HackerOne report, but the CVSS base score is only 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N); there is no CISA KEV listing and no EPSS data was provided.
Let me synthesize. CVE-2026-86465: Apache Airflow Akeyless provider secrets backend team-scope guard bypass via user-controlled key. Affected: apache-airflow-providers-akeyless before 0.3.1. Fix: 0.3.1. PR: https://github.com/apache/airflow/pull/72646. Similar class to Azure Key Vault, Yandex Lockbox, Amazon secrets backends CVEs. Multi-team deployments using Akeyless secrets backend; single-team not affected. Reachable from ordinary DAG code via Execution API Variables route accepting path-shaped key. DAG author scoped to one team can read secrets belonging to another team — info disclosure (cross-tenant secret access). CVSS: N/A provided. My assessed vector: PR:L (requires DAG author privileges / authenticated user), AV:N, AC:L, UI:N, S:C? Scope change — impacts another team's secrets, but scope change in CVSS terms means authorization scope. Cross-team boundary crossing could be S:C. Impact C:H, I:N, A:N. So CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. That's ~8.3? Let's compute: S:C base... Actually with S:C, PR:L: exploitability = 8.22*AV(0.85)*AC(0.77)*PR(0.68)*UI(0.85) = 8.22*0.85=6.987; *0.77=5.380; *0.68=3.658; *0.85=3.110. Impact: ISCBase = 1 - (1-C)(1-I)(1-A) = 1 - (1-0.56)(1)(1) = 0.56. Scope changed: Impact = 7.52*(ISC-0.029) - 3.25*(ISC-0.02)^15 = 7.52*(0.531) - 3.25*(0.54)^15 ≈ 3.993 - ~0 = 3.993. Base = roundup(min(1.08*(3.110+3.993),10)) = roundup(7.67) = 7.7. Hmm, 7.7 High. Maybe S:C is arguable. Alternatively S:U with C:H gives: Impact = 6.42*0.56 = 3.595; exploitability 3.110; base = roundup(min(1.08*6.705,10)) = roundup(7.24)=7.3. Either way ~7.3-7.7. Actually, "moderate" severity per Apache. Hmm. Apache's own severity is "moderate". But my assessment... I'll go with S:C? Let's think: the vulnerable component is the Akeyless backend; the impact is a different team's secrets. CVSS scope change refers to impact on components beyond the vulnerable component's security authority. The secrets backend... Hmm. This is a classic cross-tenant autho
A privilege escalation in KEDA 2.20.2 and earlier lets a namespace administrator who can create TriggerAuthentication and ScaledObject resources point hashiCorpVault.address at an endpoint they control and select Kubernetes authentication without supplying a credential; KEDA then logs in to that endpoint using the operator pod's projected ServiceAccount token, handing the attacker the operator's cluster-wide permissions including broad Secret reads and workload or admission-related operations. The prior CVE-2025-68476 JWT-shape filter does not block this path because the operator token's subject is a Kubernetes ServiceAccount, so it passes the filter. Exploitation is authenticated (CVSS PR:L) and gated by tenant-level RBAC to create those CRDs, but it is most dangerous in multi-tenant clusters where namespace admins are untrusted relative to the cluster-scoped operator; there is no public exploit code identified at time of analysis, and the issue is fixed in 2.21.0 via audience enforcement plus an outbound Vault-address allowlist.
Information exposure in the Dell Terraform Provider for OME, versions 1.0.0 through 1.2.3, occurs when the provider's API client error-handling path writes sensitive information into an externally accessible file or directory (CWE-209). Dell rates this CVSS 3.1 8.6 (High) with a remote, unauthenticated vector (AV:N/PR:N/UI:N/S:U/C:H/I:L/A:L), but independent assessment maps realistic exploitation to AV:L/AC:L/PR:N/UI:N/C:H/I:N/A:N, because an attacker must already be able to read wherever the provider's error output is persisted - typically shared log aggregation, publicly readable CI/CD output, or exposed Terraform state/debug artifacts - rather than reaching a directly network-exposed service. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor's AV:N vector should be validated against Dell DSA-2026-434 before treating this as a remotely exploitable unauthenticated issue.
Dell Terraform Provider for Redfish versions before 1.6.2 exposes Redfish BMC traffic, including credentials, to man-in-the-middle interception because TLS certificate verification is unconditionally disabled in its base HTTP transport. This critical-severity flaw (CVSS 9.0) allows an unauthenticated remote attacker who occupies a MITM position to capture or alter sensitive Redfish API communications, though exploitation is condition-gated to active provider-to-BMC traffic windows and is materially lower risk on trusted, isolated management segments. No public exploit identified at time of analysis; Dell recommends upgrading to 1.6.2.
Weak authentication handling in Microsoft's Azure Key Vault integration libraries allows unauthenticated remote attackers to bypass a security feature, with high confidentiality and integrity impact but no availability impact. The exposure is limited to applications and services that depend on specific vulnerable client SDK versions - the Python packages azure-keyvault-administration (<4.7.1), azure-keyvault-securitydomain (<1.0.0b3), and azure-keyvault-certificates/secrets/keys (<4.11.2), plus the .NET packages Azure.Security.KeyVault.Certificates/Secrets/Keys (<1.0.1); deployments already on patched versions are not exposed. Although the CVSS 3.1 vector (7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) indicates no authentication or user interaction is required, the High Attack Complexity reflects a meaningful non-trivial precondition - a timing or race window, a specific configuration, or an intermediary network position - rather than a single-request exploit of a default setup; no public exploit code has been identified at time of analysis, and this is a moderate-priority issue rather than an urgent fire drill.
Memory corruption in MongoDB libmongocrypt lets an authenticated actor who can modify key vault documents - or a malicious or compromised MongoDB server - crash or corrupt the memory of any client application that has Client-Side Field Level Encryption (CSFLE) or Queryable Encryption enabled. The trigger is a crafted key document containing duplicate masterKey fields, which causes provider-specific KMS data to be mis-typed during key-document cleanup, producing invalid memory access and invalid frees (CWE-843 type confusion). Scored 8.7 under CVSS 4.0, while our own assessment is more conservative at CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H, placing the confirmed impact at client-side crash and memory corruption rather than proven remote code execution; no public exploit code identified at time of analysis, and exploitation requires that encryption be in use plus key-vault write privileges (PR:L) or a hostile server.
Denial of service in MongoDB libmongocrypt occurs when KMS endpoint parsing triggers an integer underflow, causing an allocation failure that terminates the application process. This can be triggered by an authenticated user with write access to the key vault collection modifying a key document, or when an application passes a KMS endpoint containing a colon after its path or query during key creation. No public exploit code has been identified at time of analysis, and the vulnerability does not allow code execution, data disclosure, or data tampering-only a crash.
Privilege escalation in HashiCorp Vault and Vault Enterprise allows an authenticated principal with delegated permissions to bypass explicit deny ACL rules by referencing a resource or policy name in non-canonical form, potentially reaching a protected resource or assigning a denied policy. Affected are Vault Community Edition before 2.1.2 and Vault Enterprise before 2.1.2, 1.21.12, 1.20.17, and 1.19.23, rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires an already high-privileged, delegated user (PR:H) operating in a policy model that depends on explicit deny rules, and no public exploit code or confirmed active exploitation was identified at time of analysis (no EPSS data was provided), so this is best handled as a defense-in-depth hardening fix rather than an emergency.
Arbitrary code execution on the Vault host is achievable in HashiCorp Vault and Vault Enterprise when a privileged operator restores a crafted Integrated Storage (Raft) snapshot in a deployment configured with Shamir seals and an external plugin directory, because stored plugin catalog entries are not consistently verified to reference binaries inside that configured directory (CWE-22 path traversal). The attacker must already hold the high privileges needed to restore a Raft snapshot (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H), and exploitation also depends on the non-default Shamir-seal-plus-external-plugin-directory configuration, so this is a genuinely serious but condition-gated vulnerability rather than a mass-exploitation threat; clusters using auto-unseal or without an external plugin directory are not affected by this path. No public exploit identified at time of analysis, and vendor-released fixes are available in Vault Community Edition 2.1.2 and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23.
Improper TLS certificate validation in the Confluent Kafka Python client's HashiCorp Vault KMS integration (confluent-kafka versions 0 through 2.14.2) allows a man-in-the-middle attacker to obtain sensitive information when the integration is used with its default configuration, which disables certificate verification. Successful exploitation requires the application to use the Vault KMS integration and the attacker to achieve a MITM position on the TLS connection to Vault, making this a conditional but significant risk (CVSS 7.4). No public exploit has been identified at the time of analysis.
Workload secrets are written to the initializer's standard output at INFO level in Edgeless Systems Contrast versions 1.9.0 through 1.12.1, so any Kubernetes principal that holds get or list permission on the pods/logs subresource in the affected namespace can read them from the container log stream. Because those workload secrets back Contrast's encrypted storage and HashiCorp Vault integration, the storage keys and Vault credentials derived from them must also be treated as compromised, giving the attacker a path to decrypt protected data and reach Vault-backed secrets. The flaw is a regression of GHSA-h5f8-crrq-4pw8 (originally fixed in 1.8.1 but never ported to the main branch), patchable in 1.12.2; there is no public exploit identified at time of analysis and no KEV listing, so risk is driven by the low barrier of an existing log-read RBAC grant rather than by active exploitation.
MCPVault, a lightweight Model Context Protocol server that exposes Obsidian vault files to AI agents, fails to block access to restricted directories such as .git, .obsidian, and node_modules in versions prior to 0.11.4. PathFilter compiles its deny-list patterns case-sensitively and matches raw path segments, so on case-insensitive macOS and Windows filesystems variants like .Git/config or .GIT/config (and on Windows, trailing-dot/space forms such as .git./config) pass both isAllowed() and isAllowedForListing() while the operating system still opens the real restricted directory. An attacker who can influence a path selected by an AI agent can then read, write, move, search, or list sensitive repository and Obsidian metadata; no public exploit code or CISA KEV entry was identified at time of analysis.
Vault secret values leak into error messages, log output, and Nomad task events in HashiCorp consul-template due to improper error handling. The vulnerability affects consul-template deployments integrated with HashiCorp Vault, where a template rendering error can inadvertently expose secret values to any downstream surface that receives error text - including Nomad task event logs readable by lower-privileged operators. The scope-changed CVSS vector (S:C) reflects that the primary harm falls on systems outside consul-template itself: Vault secrets meant to be accessed only by privileged services instead persist in Nomad task events and logging infrastructure accessible to broader audiences.
Authorization bypass in HashiCorp Consul's Connect service mesh allows a low-privileged authenticated service to communicate with destination services it is not authorized to reach. The flaw originates in Consul's Envoy RBAC rule generation: unescaped special characters in service names, namespaces, or partitions cause the generated matching rules to be overly permissive, defeating the Connect intentions authorization model. No public exploit or CISA KEV listing exists at time of analysis; fixes are available across Consul open-source and Enterprise release trains.
Authorization bypass in HashiCorp Consul's catalog node-write path allows any authenticated principal holding a node-write token-scoped to any node name whatsoever-to delete a different node's catalog registration and seize that node's identity within the service mesh. All Consul open-source and Enterprise versions prior to the fixed releases are affected, making shared or multi-tenant Consul clusters with delegated node-write tokens particularly exposed. No public exploit code or active exploitation has been identified at time of analysis, but the low access complexity and the typically discoverable nature of node IDs make this a credible lateral-movement and disruption vector in production service-mesh deployments.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Sensitive-file exposure in the openssl-encrypt pip package (openssl_encrypt) at versions <= 1.4.8 stems from its 'Encrypted USB Workspace' feature writing a marker that falsely declares the workspace AES-256-GCM encrypted while the derived key is never applied and the directory remains in cleartext. Users who trust the branding and store files in the workspace leave them fully readable on the removable media, so anyone with physical possession of the USB device can recover the data. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but the failure silently defeats the product's core security promise.
Path traversal in Atlantis workspace handling (versions 0.19.8 through 0.44.x) allows authenticated users to escape the intended workspace directory boundary, triggering os.RemoveAll and os.MkdirAll operations on arbitrary filesystem paths with Atlantis process privileges. A crafted workspace value such as '../../../../../../../../tmp/f1-canary' - supplied via repository atlantis.yaml or authenticated /api/plan API input - causes Atlantis to operate on out-of-bounds directories before Terraform rejects the invalid workspace name. A working proof-of-concept is documented in GHSA-26w5-6g95-gj28; the vulnerability is not in CISA KEV and no public exploit kit has been identified at time of analysis.
Improper TLS certificate validation in Splunk SOAR's CyberArk REST client exposes all credential vault traffic to interception and tampering by a network-positioned attacker. Versions below 8.6.0 are affected when a CyberArk REST credential manager integration is configured; the client accepts any server certificate without verification, making TLS sessions transparent to a man-in-the-middle. No public exploit code has been identified at time of analysis, and the vulnerability is absent from the CISA KEV catalog, but the high confidentiality and integrity impact on privileged credential data warrants priority remediation in environments relying on CyberArk for SOAR playbook secrets.
Server-side request forgery in the Red Hat Ansible Automation Platform 2 Controller's HashiCorp Vault credential plugin lets an authenticated user with credential-creation rights force the controller pod to leak its own Kubernetes service account token. When a HashiCorp Vault Secret Lookup credential configured for kubernetes_role authentication is tested, the kubernetes_auth() routine in awx_plugins/credentials/hashivault.py transmits the pod token to an attacker-supplied URL. With that token the attacker gains Kubernetes API access to control-plane namespaces, enabling full pod CRUD and secret reads including database credentials and the Django SECRET_KEY. No public exploit identified at time of analysis, and the flaw is not on the CISA KEV list.
Path traversal (CWE-22) in HashiCorp Packer's third-party plugin installer through version 1.15.4 permits a crafted plugin archive to write files outside the intended extraction directory, enabling code execution on the host. Users who install plugins from malicious or compromised sources trigger the vulnerability through the normal `packer plugins install` workflow. No public exploit code has been identified at time of analysis, and a vendor-released fix is available in Packer 1.16.0.
Arbitrary file read in HashiCorp Vault Secrets Operator versions 1.3.0 through 1.4.1 lets a low-privileged Kubernetes tenant abuse the AppRole authentication's SecretIDPath configuration to read files from the operator pod's filesystem and exfiltrate their contents to an attacker-controlled endpoint, enabling privilege escalation across the cluster. Because the operator pod typically holds credentials and tokens spanning multiple tenants, a single limited-RBAC tenant can cross trust boundaries (CVSS scope change), yielding a 9.6 rating. No public exploit identified at time of analysis, but the low attack complexity and multi-tenant blast radius make this a high-priority patch.
Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.
Unauthenticated denial of service in HashiCorp Consul's external gRPC listeners allows remote attackers to exhaust agent file descriptors, goroutines, and memory by flooding incomplete connections, rendering the agent unreachable to legitimate clients. Both Consul Community Edition and Consul Enterprise versions 1.13.0 through 2.0.2 are affected - a span covering nearly three years of releases. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 7.5 score and AV:N/AC:L/PR:N profile reflect a straightforwardly exploitable network condition requiring no attacker authentication or user interaction.
Command injection in sysPass's backup service allows any authenticated administrator to execute arbitrary OS commands as the web server process user by storing shell metacharacters in the backup path configuration setting and triggering a backup operation. Because sysPass is a self-hosted password manager, successful exploitation grants direct read access to the master encryption key and entire credential vault, enabling mass credential disclosure and lateral movement to every system whose passwords are stored in sysPass. A public proof-of-concept is available via the referenced gist (https://gist.github.com/W40X/6747ba1b7da7bb69b0c0e162628df279); no CISA KEV listing was identified at time of analysis.
Cross-namespace traffic hijacking in Traefik's Kubernetes Gateway API provider allows a low-privileged tenant to redirect another namespace's HTTP, GRPC, TCP, or TLS traffic to an attacker-controlled backend. The root cause is a non-injective route identity scheme: namespaces and route names are hyphen-concatenated without field delimiters, so namespace=team/route=a-app and namespace=team-a/route=app produce the identical key httproute-team-a-app-..., and the later-loaded route silently overwrites the earlier one via maps.Copy. No public exploit identified at time of analysis as a KEV entry, but a full proof-of-concept bash script is publicly available and was verified against the official traefik:v3.7.8 image. All Traefik v3 releases prior to v3.6.25 and v3.7.10 are affected.
Missing admin authorization on the embedding management API in Odysseus allows any authenticated non-admin user to overwrite or delete the server-wide embedding backend configuration, redirecting all subsequent embedding operations - including chat messages, RAG queries, memory entries, and vault text - in plaintext to an attacker-controlled URL. All deployments running any version prior to commit bf325f6 are affected. A public exploit and detailed write-up are available, and the CVSS 4.0 score of 8.7 (PR:L) reflects the low barrier to exploitation for any account holder.
Server-side request forgery in bank-vaults vault-secrets-webhook (<= 1.22.2) lets a low-privileged tenant with ConfigMap or Secret create/update rights in any watched namespace force the cluster-wide admission webhook to make attacker-controlled outbound HTTP requests and exfiltrate ServiceAccount JWTs. The webhook trusts the vault.security.banzaicloud.io/vault-addr annotation with no scheme validation or host allowlist, then synchronously mints a SA token (via cluster-wide serviceaccounts/token:create) and POSTs it to the attacker's address, which can be replayed against the real Vault. A vendor patch (v1.23.1) exists and the reporter published a working PoC, but there is no public exploit identified in the wild and the flaw is not in CISA KEV.
Path traversal and query parameter injection in hashi-vault-js (npm, versions ≤ 0.5.1) allow an attacker who can influence identifiers passed to the library to redirect Vault API requests to arbitrary endpoints - including administrative paths such as `/v1/sys/seal` - or inject unauthorized query parameters, all executed under the permissions of the application's configured Vault token. The vulnerability arises because `Vault.js` contains zero calls to `encodeURIComponent()`, concatenating every caller-supplied identifier directly into HTTP URL strings. Two attack vectors are dynamically confirmed in the GHSA advisory: path traversal via `../../sys/seal` as a secret name, and query injection via `1&list=true` as a version value. No public standalone exploit tool has been identified and this CVE is not listed in the CISA KEV catalog.
Cross-session token leakage in HashiCorp consul-mcp-server 0.1.0 through 0.1.3 allows one client's Consul authentication token to bleed into requests issued by other clients when the server runs in stateless mode, effectively enabling an attacker to act against Consul with a victim's credentials. HashiCorp rated this CVSS 10.0 (scope-changed) because the borrowed token grants the attacker the victim's full Consul read/write authority across a trust boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; the fix is consul-mcp-server 0.1.4.
Server-Side Request Forgery in HashiCorp's consul-mcp-server 0.1.0 through 0.1.3 lets a connected client override the server's configured Consul backend address through an untrusted request header, redirecting the server's Consul API calls to an attacker-controlled endpoint and exfiltrating the privileged Consul token held by the server. The flaw carries a CVSS 8.6 (scope-changed, high confidentiality impact) and is fixed in 0.1.4; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Credential reuse in Terraform MCP Server allows cross-tenant token leakage, enabling unauthorized tool execution on behalf of other users. The vulnerability affects versions prior to 1.1.0 when the server is run in streamable-HTTP stateless transport mode. No public exploit code is known, but the critical CVSS score and network attack vector indicate high potential risk.
Authorization bypass in HashiCorp's terraform-mcp-server (versions 0.3.0 through 1.0.x) lets an attacker who obtains another user's MCP session identifier execute their own tool calls under the victim's Terraform credentials when the server runs in streamable-HTTP stateful transport mode. Rooted in a session fixation weakness (CWE-384), the flaw carries a CVSS 8.9 with a scope change, meaning cross-user credential misuse against managed infrastructure. No public exploit identified at time of analysis; EPSS is low (0.27%) and CISA SSVC records exploitation as none, indicating no observed active exploitation.
Server-side request forgery in HashiCorp terraform-mcp-server before 1.1.0 allows unauthenticated remote attackers to redirect Terraform API requests and steal server-side authorization tokens via the streamable-HTTP transport. The vulnerability, tracked as CVE-2026-14869, permits an attacker to control the destination of outbound requests, leading to token exposure. No public exploit or active exploitation has been reported at this time.
Privilege escalation in sysPass 3.2.11 allows authenticated users with the PUBLICLINK_CREATE profile flag to decrypt passwords of arbitrary vault accounts and store them in public links, enabling unauthenticated retrieval if the link hash is obtained. No active exploitation is confirmed, but public exploit code exists; EPSS probability is low (0.18%).
Missing object-level authorization in sysPass through 3.2.11 allows API token holders to enumerate account metadata, overwrite passwords, and delete any account across the vault without per-account access controls. A public proof-of-concept is available, though EPSS indicates low exploitation probability (0.22%).
Authenticated attackers can bypass access controls in sysPass 3.2.11 and earlier to access, download, or delete any account file attachment, regardless of their ACL permissions, by exploiting missing authorization checks in AccountFileController. Public exploit code is available, but the EPSS score of 0.22% indicates low likelihood of widespread exploitation.
Authentication bypass in Microsoft Azure Key Vault lets a remote, unauthenticated attacker elevate privileges over the network and gain unauthorized access to the secrets, keys, and certificates the service protects. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) rates it 9.8 Critical with full confidentiality, integrity, and availability impact. A vendor patch is available; there is no public exploit identified at time of analysis, and EPSS exploitation probability is low (0.70%, 49th percentile) despite CISA SSVC flagging the flaw as automatable with total technical impact.
Server-side request forgery and internal repository exfiltration in Gitea before 1.27.0 lets a low-privileged authenticated user bypass the migration URL allow/block list by supplying a permitted public Git URL that HTTP-redirects the server's git subprocess to an otherwise-blocked internal endpoint. Because Gitea validates only the originally submitted URL while git runs with its default http.followRedirects=initial, the redirected internal Git repository is cloned into an attacker-controlled repository, and pull mirrors keep re-fetching it on schedule. No public exploit identified at time of analysis; a vendor-authored local proof-of-concept confirmed the redirect is followed to 127.0.0.1, and EPSS/KEV data were not supplied.
Local File Read in Anyquery's Server Mode lets unauthenticated network attackers exfiltrate arbitrary files (e.g. /etc/passwd, ~/.ssh/id_rsa) readable by the server process. When `anyquery server` is running and reachable, any client speaking the MySQL wire protocol can issue native SQLite CREATE VIRTUAL TABLE statements against built-in reader modules such as csv_reader or log_reader to point at restricted paths, with no authentication or credentials required (CVSS 3.1 base 7.5, C:H/I:N/A:N). A working proof-of-concept is published in the GHSA advisory, so publicly available exploit code exists; there is no CISA KEV listing or EPSS score in the provided data.
Authorization bypass in Sonatype Nexus Repository 3's component upload API lets an account holding only read/browse privileges on a Swift, Terraform, or Conda hosted repository push arbitrary artifacts, defeating the intended write-permission check (CWE-862). The flaw affects the specific upload paths for these three formats and enables unauthorized artifact publishing that can poison downstream builds. No public exploit identified at time of analysis; Sonatype has shipped a fix in release 3.94.0.
Server-side request forgery in the Ruby css_parser gem (< 3.0.0) lets a remote unauthenticated attacker force the parsing server to issue arbitrary HTTP/HTTPS GET requests, and via an attacker-controlled 3xx redirect to a file:// URI, escalate to arbitrary local file disclosure. The flaw sits in CssParser::Parser#read_remote_file, reachable through load_uri! and any add_block! call that supplies base_uri: - Premailer being the canonical consumer - so a single attacker-planted @import url(...) in parsed CSS reaches the sink. Publicly available exploit code exists (author-supplied PoC); there is no public exploit identified as being used in active campaigns, and it is not listed in CISA KEV.
Container-to-host sandbox escape in HashiCorp Nomad and Nomad Enterprise lets an authenticated job submitter using the Docker task driver bind-mount an arbitrary host path into their container even when volume bind mounts are administratively disabled, enabling read and write access to files on the underlying host. The scope-changing flaw (CVSS 3.1 8.7) affects the Community and Enterprise editions and is fixed in Nomad 2.0.4 (CE), and Enterprise 2.0.4, 1.11.8, and 1.10.14. There is no public exploit identified at time of analysis and it is not on CISA KEV.
Account takeover in self-hosted Bitwarden Server before 2026.6.0 lets a low-privileged organization member steal any other member's vault key and a victim-scoped access token. The POST /auth-requests/admin-request handler never verifies that the email in the request body belongs to the authenticated caller (CWE-639), so an attacker can create a Trusted Device Encryption admin-approval request for a victim, bound to an attacker-controlled public key; once approved, the encrypted key material is retrievable from an unauthenticated endpoint. Publicly available exploit code exists (a VulnCheck advisory plus a public write-up), and the CVSS 4.0 base score of 9.3 reflects high confidentiality and integrity impact plus a cross-user scope change.
Host namespace escape in HashiCorp Nomad and Nomad Enterprise lets an authenticated job submitter bypass the allow_privileged control for the Docker task driver, launching containers in host PID/network/IPC namespaces to read data from the host or co-located workloads on the same client node. The flaw stems from missing authorization enforcement (CWE-862) and carries a CVSS 7.7 with a changed scope, reflecting cross-tenant impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
SQL and DDL injection in the Snowflake Terraform Provider before 2.18.0 lets an attacker who can influence pipeline workspace variables execute arbitrary SQL inside the provider's privileged Snowflake session (CWE-89), enabling data exfiltration and creation of long-lived credentials. A second flaw allows identifier-injection into user-management DDL, so accounts can be minted with attacker-controlled credentials that bypass operator-configured security controls. No public exploit identified at time of analysis; risk is authenticated/insider-driven rather than remote-unauthenticated.
Arbitrary file read in HashiCorp Terraform Enterprise allows an authenticated user to escape the intended repository boundary during VCS-based registry module ingestion, pulling files from outside the source repository into a packaged module and downloading them. Because the ingestion process runs with its own filesystem privileges, an attacker can exfiltrate sensitive files (secrets, configuration, tokens) readable by that process. Reported by HashiCorp with no public exploit identified at time of analysis; the CVSS 7.7 (scope-changed) score reflects high confidentiality impact against a self-hosted enterprise platform.
Java object deserialization in the Apache Camel camel-pqc component allows code execution in the key-management application when an attacker who can write to the backing AWS Secrets Manager secret stores a malicious serialized payload. The flaw affects Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x, where AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() calls a raw ObjectInputStream.readObject() with no class filter, so gadget side effects fire before the KeyMetadata cast. Rated CVSS 9.8 by Apache, but exploitation genuinely requires IAM write access to the specific secret; there is no public exploit identified at time of analysis and EPSS is low at 0.19% (8th percentile).
Remote code execution via unsafe Java deserialization affects the camel-pqc component of Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x. The HashiCorp Vault and AWS Secrets Manager KeyLifecycleManager implementations (and a legacy-migration path in the file-based manager) read post-quantum key metadata back with a raw ObjectInputStream.readObject() lacking any ObjectInputFilter or allow-list, so a principal able to write to the key backend can plant a gadget object that executes during normal key-lifecycle operations. No public exploit has been identified at time of analysis and EPSS is low (0.19%), but SSVC rates technical impact as total; this is an incomplete-remediation follow-on to CVE-2026-40048.
Server-side request forgery and secret disclosure in the Apache Camel camel-iggy consumer (versions 4.17.0-4.18.2 and 4.19.0-4.20.x) allow an actor able to publish to a consumed Iggy stream to inject Camel control headers such as CamelHttpUri into the Exchange. When the consumer feeds a downstream HTTP producer, the attacker redirects the server-side request to internal services or cloud metadata endpoints, and because the producer resolves Camel property placeholders on the attacker-controlled URI, environment variables, application properties, and vault secrets are exfiltrated. No public exploit identified at time of analysis, and EPSS is low (0.15%), but the confidentiality impact is rated High.
Server-side request forgery and secret disclosure in Apache Camel's camel-atmosphere-websocket component allow a remote attacker to hijack downstream server-side HTTP requests by injecting Camel control headers as WebSocket query parameters. Affecting Camel 4.0.0-4.14.7, 4.15.0-4.18.2 and 4.19.0-4.20.x, the flaw lets an attacker set CamelHttpUri to redirect internal HTTP calls (e.g., to cloud metadata endpoints) and force resolution of Camel property placeholders, leaking environment variables, application properties and vault secrets. Where the WebSocket endpoint is exposed without authentication the issue is unauthenticated (CVSS 7.5); there is no public exploit identified at time of analysis and EPSS is low (0.24%).
Server-side request forgery and secret disclosure in Apache Camel's camel-vertx-websocket component (versions 4.0.0-4.14.7, 4.15.0-4.18.2, and 4.19.0-4.20.x) let a WebSocket client inject Camel-internal control headers such as CamelHttpUri because inbound query/path parameters are copied into the Exchange header map without a HeaderFilterStrategy. In routes that bridge the WebSocket consumer into a downstream HTTP producer, an attacker can redirect the server-side HTTP request to internal services or cloud metadata endpoints, and because the HTTP producer resolves Camel property placeholders on the attacker-supplied URI, environment variables, application properties, and vault secrets are resolved and exfiltrated. When the WebSocket endpoint is exposed without authentication (PR:N per CVSS), this is reachable by an unauthenticated remote attacker; there is no public exploit identified at time of analysis, and EPSS is low at 0.24%.
Credential disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows any authenticated user to retrieve plaintext OAuth tokens, vault passwords, and SSH keys by sending forged Worker messages to the Event-Driven Ansible websocket endpoint. The /api/eda/ws/ansible-rulebook endpoint fails to verify permissions on activation_id values, enabling lateral credential theft across tenants. No public exploit identified at time of analysis, but the low attack complexity and scope-changed CVSS of 9.6 make this a high-priority patch.
Denial of service in CyberArk Privileged Access Manager (PAM) Self-Hosted Vault allows remote attackers to terminate the Vault service by sending unexpected input under specific configuration scenarios, affecting versions prior to 15.0.3, 14.6.5, 14.2.7, and 14.0.8. Disclosed by Palo Alto Networks (which now owns CyberArk) via Security Bulletin CA26-17 with no public exploit identified at time of analysis, the CVSS 4.0 base score of 8.7 reflects the network-reachable, unauthenticated attack path against a security-critical service. The flaw is a CWE-400 resource/input handling issue that produces a localized DoS rather than code execution or data exposure.
Arbitrary file write in the Altium Enterprise Server Vault Service allows authenticated users to escape the configured storage root via the UploadController image upload endpoint and place content-controlled files anywhere the service account can write. The flaw (CVSS 4.0 base 9.4, CWE-22) escalates to remote code execution, service takeover, or denial of service by overwriting application binaries, configuration files, or dropping payloads in web-accessible directories. No public exploit identified at time of analysis, and Altium 365 cloud deployments are explicitly out of scope.
Unauthenticated file disclosure and arbitrary file read in Altium Enterprise Server prior to 8.1.1 allows any network-reachable attacker to forge signed Vault download URLs using a hard-coded key shipped identically across all installations. Chained with a co-located path traversal in the same download endpoint (and optionally CVE-2026-9152 for enumeration), an attacker can read arbitrary server-side files including configuration and key material, leading to full server compromise. No public exploit identified at time of analysis; CVSS 4.0 score is 10.0 and Altium 365 SaaS is not affected because cloud deployments use object storage rather than the local filesystem.
Missing authentication in the Altium 365 SearchService lets an unauthenticated network attacker who knows a target workspace identifier interact with that workspace's search index across tenant boundaries via a legacy SOAP endpoint. Affecting Altium 365 cloud deployments (on-premise Altium Enterprise Server is not affected), it enables reading indexed component, project, folder, and user metadata and injecting, modifying, or deleting search index entries - an authentication bypass with no public exploit identified at time of analysis, though CISA's SSVC framework marks the flaw automatable with total technical impact.
Supply-chain compromise of the npm package @beproduct/nestjs-auth (versions 0.1.2 through 0.1.19) delivered the Mini Shai-Hulud worm payload via a malicious postinstall script, harvesting npm, GitHub, AWS, and HashiCorp Vault credentials from any developer or CI host that ran npm install during a 2h37m publication window on 2026-05-11. Confirmed actively exploited during that window via an attacker-controlled npm publish token; clean version 0.1.20 republishes the original 0.1.1 source tree. CVSS 10.0 reflects the unauthenticated, network-driven supply-chain delivery and scope change into the install environment.
Unauthenticated agent token theft in Coder v2 (self-hosted developer workspace platform) stems from azureidentity.Validate() verifying the PKCS#7 signer's certificate chain but skipping signature verification of the signed content itself. Remote attackers who know a target VM's vmId (a UUIDv4) can forge a PKCS#7 envelope containing a legitimate Azure certificate alongside attacker-controlled content and POST it to the unauthenticated /api/v2/workspaceagents/azure-instance-identity endpoint to receive the victim workspace agent's session token, which then unlocks Git SSH keys, OAuth tokens for GitHub/GitLab/Bitbucket, and workspace secrets. No public exploit identified at time of analysis, but the vulnerability is vendor-confirmed via GHSA-6x44-w3xg-hqqf and a detailed root-cause analysis with attack-path diagram is published.
Server-Side Request Forgery in Tenable Terrascan v1.18.3 and prior allows unauthenticated remote attackers to coerce the server into fetching arbitrary URLs, including file:// URIs that enable local file disclosure. The flaw is triggered when Terrascan runs in server mode and parses uploaded ARM or CloudFormation templates whose templateLink.uri, parametersLink.uri, or AWS::CloudFormation::Stack TemplateURL fields point to attacker-controlled destinations. No public exploit identified at time of analysis, and because Terrascan was archived in August 2023, no patch will ever be released.
Server-Side Request Forgery in Tenable's Terrascan IaC scanner (versions 1.18.3 and prior) lets unauthenticated remote attackers read arbitrary local files and exfiltrate ~/.netrc credentials when the tool runs in server mode. Because Terrascan was archived in August 2023, no vendor patch will ever be released, and the daemon binds to 0.0.0.0 with no authentication by default. No public exploit identified at time of analysis, but the CVSS 4.0 score of 9.2 reflects trivial network-reachable abuse paired with significant confidentiality scope change.
Authenticated code execution on Nomad client hosts is possible in HashiCorp Nomad and Nomad Enterprise 1.10.0 through versions prior to 2.0.1 via a path traversal flaw in the dynamic host volume feature. A submitter with volume-creation privileges can escape the intended volume directory and write to or execute code in arbitrary locations on the client node's filesystem, gaining code execution outside the intended sandbox. This flaw is not in CISA KEV and has no public exploit identified at time of analysis; EPSS probability is low at 0.03%.
Full administrative database takeover in Google Cloud AlloyDB for PostgreSQL affected clusters provisioned via Terraform or the REST API before 2025-11-03, where those provisioning paths applied an insecure default password. A remote attacker with network reachability to such a cluster could authenticate as a privileged account and gain complete control of the database. There is no public exploit identified at time of analysis, and the EPSS probability is very low (0.04%, 12th percentile), consistent with the SSVC assessment of no observed exploitation.
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actions exploitation. Attackers combined pull_request_target misconfiguration, Actions cache poisoning, and OIDC token memory extraction to publish malicious code under the legitimate TanStack identity. Installing any affected version executes a 2.3 MB obfuscated payload that exfiltrates AWS/GCP/Kubernetes credentials, npm tokens, GitHub secrets, SSH keys, and HashiCorp Vault tokens over encrypted Session/Oxen messenger infrastructure. The payload propagates by republishing victim-maintained packages with identical injection. Socket.dev and the TanStack team confirmed the incident via GHSA-g7cv-rxg3-hmpx. No EPSS or CISA KEV data available for this recent supply-chain attack. CVSS 9.6 reflects the cross-scope credential theft impact (S:C/C:H/I:H), though exploitation requires user-initiated package installation (UI:R).
Improper authorization in Vaultwarden (self-hosted Bitwarden-compatible server) before 1.35.5 lets an authenticated user who was invited as an organization owner and has accepted-but not yet been confirmed-invoke POST /api/ciphers/purge to hard-delete every cipher and attachment in the organization. The endpoint checks only that membership type is Owner and omits the required Confirmed-status check, enabling irreversible organization-wide data loss. There is no public exploit identified at time of analysis, EPSS is negligible (0.04%), and SSVC records no known exploitation.
Cross-organization authorization bypass in Vaultwarden (the Rust-based, self-hosted Bitwarden-compatible server) prior to 1.35.5 lets an attacker who holds Admin rights in one organization pivot into a second organization where they are only a low-privileged member. Because group-management endpoints persist arbitrary MembershipId and CollectionId values without checking org consistency (CWE-285), the attacker can bind their foreign Org B membership into an accessAll Org A group and read - then write - Org B vault data via /api/sync and /api/ciphers. A POC is referenced in the SSVC data (publicly available exploit code exists); it is not in CISA KEV and EPSS is very low (0.03%), consistent with a targeted, multi-step abuse rather than mass exploitation.
Authentication bypass in UltraDAG Core blockchain allows remote unauthenticated attackers to drain all pocket-derived sub-addresses on smart accounts, completely bypassing vault delays and daily spending limits. The StateEngine fails to resolve pocket addresses to their parent account during policy enforcement, treating virtual pocket addresses as unrestricted accounts. Confirmed actively exploited (CISA KEV). Vendor-released patch: commit fb6ef59 resolves pocket-to-parent mapping before all policy checks. EPSS data unavailable but attack vector is network-accessible with no complexity (CVSS 4.0 AV:N/AC:L/PR:N), making this a critical priority for any UltraDAG deployment using smart account pockets.
Server-side authentication bypass in the OpenTelemetry Collector Contrib azureauthextension (v0.124.0-v0.150.0) lets any holder of a valid Azure access token minted for the collector's service principal authenticate to any receiver configured with auth: azure_auth. The extension never validates bearer tokens as JWTs; it mints its own token using the client-supplied Host header as the scope and compares strings, so a token issued for an unrelated Azure resource (ARM, Graph, Key Vault, Storage) is accepted if the attacker sets a matching Host. No CISA KEV listing and EPSS is very low (0.05%), but the vendor advisory (GHSA-pjv4-3c63-699f) documents a working proof-of-concept for both replay and scope-confusion variants.
Network-accessible denial-of-service in HashiCorp Boundary workers allows unauthenticated remote attackers to block legitimate worker connections by manipulating TLS handshake timing during node enrollment. Attackers can connect to the worker authentication listener and intentionally delay or withhold client certificates, causing connection handlers to block and preventing legitimate workers from enrolling or routing traffic. Both Community Edition and Enterprise versions prior to 0.21.3, 0.20.3, and 0.19.5 are vulnerable. EPSS data not provided; no CISA KEV listing indicating limited observed exploitation. Vendor-confirmed vulnerability with patches released across three active release branches.
HashiCorp Vault unauthenticated denial-of-service vulnerability allows remote attackers to block critical administrative operations by monopolizing the single operation slot for root token generation and rekey workflows. Affects all Vault Community and Enterprise versions prior to 2.0.0. No active exploitation confirmed (EPSS 3rd percentile), but attack is trivially automatable per CISA SSVC framework. HashiCorp released patches in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.
Token leakage in HashiCorp Vault and Vault Enterprise (0.11.2 up to 2.0.0, 1.21.5, 1.20.10, and 1.19.16) occurs when an auth mount is configured to pass through the 'Authorization' header and that same header is used to authenticate to Vault; in this case Vault forwards the caller's Vault token onward to the auth plugin backend. An authenticated client's token is thereby exposed to a plugin backend that should never see it, enabling potential impersonation and unauthorized secret access. No public exploit identified at time of analysis, and EPSS exploitation probability is negligible (0.01%, 3rd percentile).
HashiCorp Vault's KVv2 secrets engine allows authenticated users with glob-based policy access to delete secrets outside their authorization scope, causing denial-of-service across versions 0.10.0 through 1.x. The flaw stems from improper access control (CWE-288) in policy glob evaluation during delete operations. Exploitation requires valid Vault credentials with specific policy patterns but does not permit cross-namespace deletion or secret data exfiltration. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0/1.21.5/1.20.10/1.19.16. No active exploitation confirmed (EPSS 0.01%), but CVSS 8.1 reflects high integrity and availability impact for authenticated attackers.
Arbitrary file read vulnerability in HashiCorp go-getter library versions up to 1.8.5 enables unauthenticated remote attackers to access sensitive files from the target filesystem through specially crafted git operation URLs. The vulnerability permits confidentiality breach without authentication requirements, affecting network-accessible services utilizing the library for repository cloning or fetching operations. Fixed in version 1.8.6; go-getter/v2 branch unaffected. No public exploit identified at time of analysis.
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks against Dgraph graph database servers (v24.x, v25.x prior to v25.3.1) via the admin API's restoreTenant mutation. The mutation bypasses all authentication middleware due to missing authorization configuration, allowing attackers to provide arbitrary backup source URLs (including file:// schemes for local filesystem access), S3/MinIO credentials, Vault configuration paths, and encry
Authenticated users in n8n versions prior to 1.123.23 and 2.6.4 can bypass external secrets permission checks to retrieve plaintext secret values from configured vaults by referencing secrets by name in credentials, even without list permissions. This allows unauthorized access to sensitive vault-stored credentials without requiring admin or owner privileges, provided the attacker knows or can guess the target secret name. Public exploit code exists for this vulnerability.
An integrity check vulnerability in Cryptomator for Android prior to version 1.12.3 allows attackers to tamper with the vault configuration file, enabling a man-in-the-middle attack against the Hub key loading mechanism. Attackers who can modify the vault.cryptomator file can mix legitimate authentication endpoints with malicious API endpoints to exfiltrate tokens from users unlocking Hub-backed vaults. With a CVSS score of 7.6 and requiring low attack complexity with user interaction, this vulnerability poses a moderate risk to affected users in environments where vault configuration files can be altered.
A man-in-the-middle vulnerability in Cryptomator for iOS versions prior to 2.8.3 allows attackers who can modify the vault.cryptomator configuration file to intercept authentication tokens by substituting malicious API endpoints while maintaining legitimate authentication endpoints. This affects users unlocking Hub-backed vaults in environments where attackers have write access to vault configuration files. No evidence of active exploitation (not in CISA KEV) has been reported, and patches are available.
Cryptomator's Hub-based unlock flow contains a protocol downgrade vulnerability that allows the application to communicate with Hub endpoints over plaintext HTTP instead of enforcing HTTPS. Cryptomator versions prior to 1.19.1 are affected, exposing OAuth bearer tokens, key-loading traffic, and endpoint-level trust decisions to network interception and tampering by active attackers. This is a verified GitHub security advisory with patches available in version 1.19.1, though no EPSS score or KEV listing indicates limited evidence of active exploitation.
Cryptomator versions prior to 1.19.1 contain an integrity check vulnerability that allows attackers to tamper with the vault.cryptomator configuration file, enabling man-in-the-middle attacks during Hub key loading. Attackers can mix legitimate authentication endpoints with malicious API endpoints to exfiltrate access tokens from users unlocking Hub-backed vaults in environments where vault configuration files can be modified. The CVSS score of 7.6 indicates high severity with network attack vector requiring low privileges and user interaction, though no active exploitation (KEV) or public POC has been reported at this time.
An authorization bypass vulnerability exists in the Vault secrets back-end implementation of Canonical's Juju orchestration tool, allowing authenticated unit agents to perform unauthorized updates to secret revisions beyond their intended scope. Juju versions 3.1.6 through 3.6.18 are affected, and attackers with sufficient information can poison any existing secret revision within the Vault secret back-end scope. With a CVSS score of 7.6 (High severity) featuring network attack vector, low complexity, and high integrity impact, this represents a significant security concern for Juju deployments using Vault as their secrets back-end, though no active exploitation (KEV) status or EPSS score was provided in available data.
Insecure password saving enforcement in Devolutions Remote Desktop Manager 2025.3.
Dell Terraform Provider for OME versions 1.0.0 through 1.2.3 inserts sensitive provider configuration data into log files, so an authenticated, low-privileged remote attacker who can read those logs may obtain limited confidential information about the managed environment. Scored 4.3 (Medium) as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, the issue requires prior low-level access plus reachability of the log destination, with no integrity or availability impact. No public exploit code has been identified at time of analysis, and no confirmed active exploitation is reported, so practical risk is governed by what the provider actually writes to logs and how tightly log retention and access are controlled.
Sensitive information handled by the redfish_certificate resource in the Dell Terraform Provider for Redfish (versions 1.1.0 through 1.6.1) can be exposed to unauthorized parties through CWE-532 weakness, most plausibly via Terraform debug logs, state files, or CI/CD console output. Exploitation requires a high-privileged actor operating within the Terraform workflow (PR:H) who also has access to wherever the sensitive data is written, so realistic abuse is confined to users already close to the automation pipeline; the bounded version range and low confidentiality impact further constrain it. The vendor scores this CVSS 4.3, and our independent assessment concurs at 4.3 with confidentiality-only impact, making it a low-severity information-exposure issue rather than an urgent patching priority. No public exploit identified at time of analysis.
Path traversal in HashiCorp go-getter's S3 and GCS directory-download handling lets files be written outside the requested destination, affecting go-getter before 1.8.10 and go-getter/v2 before 2.2.5. Unauthenticated remote attackers (CVSS PR:N) can only succeed if a victim initiates a download against an attacker-influenced S3 or GCS bucket that contains crafted object keys with traversal sequences, which is why the vector requires user interaction (UI:R) and carries high attack complexity (AC:H); the resulting impact is integrity-only (CVSS 5.3, I:H with no confidentiality or availability effect). No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor patches are available.
Cross-namespace privilege escalation in HashiCorp Vault Enterprise allows an authenticated token holding a specially crafted policy name containing path-traversal constructs to have its policy resolved against a different namespace - including the root namespace - thereby gaining capabilities granted by policies it should never reach. Only Vault Enterprise deployments with namespaces actually configured are exposed; Vault Community Edition does not implement namespaces and is explicitly not affected. Exploitation requires a valid token (CVSS PR:L, authenticated) and the resulting privilege gain is bounded by whatever policies exist in the traversed namespace, making this a moderate-priority privilege-escalation issue rather than a mass-exploitation threat - no public exploit code has been identified at time of analysis and no EPSS or KEV data was supplied.
HashiCorp Vault's PKI secrets engine ACME server, when running under the default directory policy, can issue certificates that contain identity claims the ACME challenges never validated, allowing an unauthenticated ACME client (CVSS vector PR:N/UI:N) to obtain a certificate for an identity it does not control and impersonate that identity toward systems that trust the affected Vault PKI mount. The issue is a configuration-dependent certificate-integrity flaw (CVSS 5.9, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) rather than an urgent remote-code or data-exposure bug: it requires a PKI mount with the ACME server enabled under the default directory policy and relying systems that actually trust certificates issued by that mount, otherwise the unverified identity has no effect. HashiCorp addressed it in Vault Community Edition 2.1.2 and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23; no public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied in the available data.
Trivy versions before 0.71.0 allow directory traversal through Terraform filesystem functions during misconfiguration scanning of untrusted input, potentially exposing sensitive files located outside the scan root. An attacker able to supply a malicious Terraform configuration (e.g., via a third-party pull request) can use relative paths like '../secret' in file() or filebase64() to include the contents of files above the scan directory in scan output. Exploitation requires the sensitive file to exist at a guessable traversal path and is confined to information disclosure (C:L) with high attack complexity; no public exploit has been identified at time of analysis.
Cross-team secret disclosure in the HashiCorp Vault secrets backend for Apache Airflow lets an authenticated Dag author scoped to one team read Vault secrets belonging to a different team in multi-team deployments. The flaw (CWE-639, authorization bypass through a user-controlled key) triggers when the team-scoped lookup misses and the backend falls back to a team-agnostic path concatenated from the unvalidated Variable key; because the Execution API Variables route accepts a path-shaped key, the traversal is reachable from ordinary Dag code. The vendor assigned no CVSS score (CVSS: N/A), while the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - read-only disclosure with scope change and no integrity or availability impact; single-team deployments are unaffected, no public exploit code has been identified at time of analysis, and the vendor-released fix is apache-airflow-providers-hashicorp 4.8.0.
Ansible Automation Platform 2's gateway permits an authenticated gateway administrator (CVSS PR:H) to create a new service key for the Controller service cluster through the API, even though service-key creation is supposed to occur only via the installer-provisioned path; the resulting key is cryptographically indistinguishable from a legitimate one, so it can be used to mint a service-authentication token that impersonates the Controller service. When the non-default gateway OIDC workload-identity endpoint is enabled (FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED) and a downstream resource server such as HashiCorp Vault trusts the gateway's OIDC signing key, the attacker can induce the gateway to sign Workload Identity Tokens for arbitrary Controller workloads and retrieve the AAP credentials bound to that workload, crossing the administrator's authorization boundary to disclose secrets (C:H, no integrity or availability impact). Exploitation requires admin privileges plus that specific non-default trust configuration, and no public exploit has been identified at time of analysis; the defect is access-gated rather than broadly exploitable.
Improper validation of parameters in GitLab CE/EE's Terraform state upload functionality allows an authenticated user holding project-level permissions to read restricted file contents on the server or cause denial of service. Affected releases are all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with fixes published in the 19.3.2 patch release. Public exploit details exist via a HackerOne report, but the CVSS base score is only 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N); there is no CISA KEV listing and no EPSS data was provided.
Let me synthesize. CVE-2026-86465: Apache Airflow Akeyless provider secrets backend team-scope guard bypass via user-controlled key. Affected: apache-airflow-providers-akeyless before 0.3.1. Fix: 0.3.1. PR: https://github.com/apache/airflow/pull/72646. Similar class to Azure Key Vault, Yandex Lockbox, Amazon secrets backends CVEs. Multi-team deployments using Akeyless secrets backend; single-team not affected. Reachable from ordinary DAG code via Execution API Variables route accepting path-shaped key. DAG author scoped to one team can read secrets belonging to another team — info disclosure (cross-tenant secret access). CVSS: N/A provided. My assessed vector: PR:L (requires DAG author privileges / authenticated user), AV:N, AC:L, UI:N, S:C? Scope change — impacts another team's secrets, but scope change in CVSS terms means authorization scope. Cross-team boundary crossing could be S:C. Impact C:H, I:N, A:N. So CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. That's ~8.3? Let's compute: S:C base... Actually with S:C, PR:L: exploitability = 8.22*AV(0.85)*AC(0.77)*PR(0.68)*UI(0.85) = 8.22*0.85=6.987; *0.77=5.380; *0.68=3.658; *0.85=3.110. Impact: ISCBase = 1 - (1-C)(1-I)(1-A) = 1 - (1-0.56)(1)(1) = 0.56. Scope changed: Impact = 7.52*(ISC-0.029) - 3.25*(ISC-0.02)^15 = 7.52*(0.531) - 3.25*(0.54)^15 ≈ 3.993 - ~0 = 3.993. Base = roundup(min(1.08*(3.110+3.993),10)) = roundup(7.67) = 7.7. Hmm, 7.7 High. Maybe S:C is arguable. Alternatively S:U with C:H gives: Impact = 6.42*0.56 = 3.595; exploitability 3.110; base = roundup(min(1.08*6.705,10)) = roundup(7.24)=7.3. Either way ~7.3-7.7. Actually, "moderate" severity per Apache. Hmm. Apache's own severity is "moderate". But my assessment... I'll go with S:C? Let's think: the vulnerable component is the Akeyless backend; the impact is a different team's secrets. CVSS scope change refers to impact on components beyond the vulnerable component's security authority. The secrets backend... Hmm. This is a classic cross-tenant autho