Search: iam.ma
137 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 4.9 | EPSS 0.4% | CVE-2026-59806gradio · Open Redirect Medium4.9EPSS 0.4%CVE Database V5CVE-2026-59806 Gradio before 6.20.0 contains an open redirect and server-side request forgery vulnerability that allows attackers to redirect users to arbitrary URLs or perform client-side SSRF by supplying unvalidated HTTP/HTTPS URLs to the file_fetch() function in the /gradio_api/file= endpoint. Attackers can craft a malicious FileData response targeting internal endpoints such as cloud metadata services to retrieve sensitive credentials including EC2 IAM role credentials. | CVE Database V5 | ||
| Medium | 5.1 | EPSS 0.3% | CVE-2026-58468nocobase · Server-Side Request Forgery (SSRF) Medium5.1EPSS 0.3%CVE Database V5CVE-2026-58468 NocoBase versions up to 2.1.20 contain a server-side request forgery (SSRF) vulnerability that allows authenticated administrators to make arbitrary outbound HTTP requests. This can be exploited via workflow request nodes, custom request action buttons, or the AI plugin. The vulnerability enables attackers to access internal network resources, including loopback addresses, private IP ranges, and cloud instance metadata endpoints, potentially leading to internal network reconnaissance and retrieval of IAM role credentials. Version 2.1.18 introduced a warning when the SERVER_REQUEST_WHITELIST is not configured, but no fix is explicitly stated. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The npm package 'iam-scripts' version 99.9.9 contains malicious code. This is identified as a malicious package threat rather than a traditional software vulnerability. There is no CVSS score or detailed technical description available. No known exploits in the wild have been reported. No patch or remediation information is provided. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package 'generate-iam-token' version 99.9.9 contains malicious code. This is identified as a malicious package threat rather than a traditional software vulnerability. There is no CVSS score or detailed technical description available. No known exploits in the wild have been reported. No patch or remediation information is provided. | GCVE Database | |||
| High | 8.8 | EPSS 0.8% | CVE-2026-46590Apache Camel · Deserialization of Untrusted Data High8.8EPSS 0.8%CVE Database V5CVE-2026-46590 Deserialization of Untrusted Data vulnerability in Apache Camel PQC component. The camel-pqc component persists post-quantum key metadata (KeyMetadata) through pluggable KeyLifecycleManager implementations. HashicorpVaultKeyLifecycleManager and AwsSecretsManagerKeyLifecycleManager read that metadata back from the configured secret backend by deserializing a Base64-wrapped value with a raw java.io.ObjectInputStream.readObject() and no ObjectInputFilter or class allow-list; the cast to KeyMetadata happens only after readObject() returns, so any readObject() side effects in a crafted object run before the type check. The same unfiltered legacy-migration read also remained in FileBasedKeyLifecycleManager (for the stored KeyPair and KeyMetadata). A principal who can write to the operator-controlled backend that holds these values - the HashiCorp Vault KV path, or the AWS Secrets Manager secret (requiring a Vault token or secretsmanager:PutSecretValue) - could store a crafted serialized object that is deserialized during normal key-lifecycle operations, potentially leading to code execution in the context of the application that manages the keys. This is an incomplete-remediation follow-on to CVE-2026-40048 (CAMEL-23200), which changed FileBasedKeyLifecycleManager to store metadata as JSON / PKCS#8 / X.509 but did not add an ObjectInputFilter, did not cover the Vault and AWS sibling managers, and left FileBasedKeyLifecycleManager's own legacy-migration deserialization unfiltered. This issue affects Apache Camel: from 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, restrict write access to the key backend so that only the application's own identity can write the camel-pqc secrets (least-privilege HashiCorp Vault policies and secretsmanager:PutSecretValue IAM), and keep the PQC key material in a backend separate from any data that less-trusted principals can write. | CVE Database V5 | ||
| Critical | 9.8 | EPSS 0.9% | CVE-2026-43867Apache Camel · Deserialization of Untrusted Data Critical9.8EPSS 0.9%CVE Database V5CVE-2026-43867 Deserialization of Untrusted Data vulnerability in Apache Camel PQC Component. The camel-pqc component persists post-quantum key metadata (KeyMetadata) through pluggable KeyLifecycleManager implementations. AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() reads that metadata back from the configured AWS Secrets Manager secret by Base64-decoding the stored value and deserializing it with a raw java.io.ObjectInputStream.readObject() and no ObjectInputFilter or class allow-list; the cast to KeyMetadata happens only after readObject() returns, so any readObject() side effects in a crafted object run before the type check. A principal who can write to the AWS Secrets Manager secret that holds this metadata (requiring secretsmanager:PutSecretValue on that secret) could store a crafted serialized object that is deserialized during normal key-lifecycle operations, potentially leading to code execution in the context of the application that manages the keys. This is the same underlying defect, in the same code path and remediated by the same fix, as CVE-2026-46590, which was reported independently and additionally covers the HashiCorp Vault and file-based sibling managers; both are incomplete-remediation follow-ons to CVE-2026-40048 (CAMEL-23200). This issue affects Apache Camel: from 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, restrict write access to the AWS Secrets Manager secret that holds the camel-pqc key metadata so that only the application’s own identity holds secretsmanager:PutSecretValue on it (least-privilege IAM), and keep the PQC key material in a secret separate from any data that less-trusted principals can write. | CVE Database V5 | ||
| Critical | 9.8 | EPSS 0.7% | CVE-2026-56140Apache Camel AWS2 SNS · Improper Input Validation Critical9.8EPSS 0.7%CVE Database V5CVE-2026-56140 Improper Input Validation vulnerability in Apache Camel AWS SNS component. The camel-aws2-sns component filters Camel headers through a component-specific HeaderFilterStrategy, Sns2HeaderFilterStrategy. Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule. For the related camel-aws2-sqs component this inbound gap was exploitable, because the Sqs2Consumer maps inbound SQS message attributes into the Camel Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, allowing a message sender to inject Camel control headers (tracked as CVE-2026-46456). camel-aws2-sns, by contrast, is producer-only: Sns2Endpoint does not support consumers (createConsumer throws UnsupportedOperationException, 'You cannot receive messages from this endpoint'), so no externally-supplied message attributes are ever mapped inbound into a Camel Exchange through SNS, and the missing inbound filter rule on Sns2HeaderFilterStrategy was therefore not reachable by an attacker. As part of the same fix (CAMEL-23506), an inbound filter rule (setInFilterStartsWith for the Camel namespace) was added to Sns2HeaderFilterStrategy so that its configuration matches the corrected Sqs2HeaderFilterStrategy and the other sibling strategies. This is a defense-in-depth alignment with no known exploit path in camel-aws2-sns. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. This is a defense-in-depth hardening change with no known exploit path in camel-aws2-sns, which is producer-only, so no urgent action or workaround is required. Users who want the aligned behaviour can upgrade to version 4.21.0, or to 4.14.8 on the 4.14.x LTS releases stream, or to 4.18.3 on the 4.18.x releases stream, which contain the change. As a general best practice, operators should continue to apply least-privilege IAM permissions on their SNS topics. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The npm package 'ripshakti' version 80.0.0 contains malicious code that executes automatically during installation. Its preinstall script collects sensitive AWS instance metadata, environment secrets, and IAM credentials, then exfiltrates this data to an attacker-controlled server. This compromises cloud IAM roles and environment secrets of any system running 'npm install' for this package. | GCVE Database | |||
| High | 8.2 | EPSS 0.4% | CVE-2026-10564IBM Langflow OSS · Server-Side Request Forgery (SSRF) High8.2EPSS 0.4%CVE Database V5CVE-2026-10564 IBM Langflow OSS 1.0.0 through 1.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker can exploit this to access internal resources including cloud metadata services (AWS/Azure/GCP IMDS), potentially exfiltrating IAM credentials and enumerating internal networks. The vulnerability can also be triggered through prompt injection in agentic workflows due to tool_mode=True exposure. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5f0097d19be676ac30ff79dffcff38f128873c80115a8a150c3eceff0422aa93) On npm install, the package's postinstall script queries the AWS instance metadata service (IMDSv1) at 169.254.169.254 for the attached IAM role and POSTs the result, along with an IMDS-reachability probe, over plain HTTP to a hardcoded bare IP (54.226.194.239:80/chain3). The published library surface (index.js) only exports two no-op console.log stubs named validate/deploy, with no real functionality — the entire effective behavior is the install-time reconnaissance against AWS-hosted installers and CI runners. The combination of a placeholder API, a generic deployment-utility name suggesting an internal/private package, and install-time recon to a hardcoded bare-IP C2 matches the dependency-confusion / internal-name-squat pattern targeting corporate build systems, where exposed IAM role names enable follow-on credential abuse against the installer's cloud environment. | GCVE Database | |||
| Critical | 9.9 | EPSS 0.3% | Critical9.9EPSS 0.3%GCVE DatabaseCVE-2026-55166 Lemur manages TLS certificate creation. Prior to 1.9.2, authenticated users could influence an ACME authority acme_url without an effective server-side destination restriction and trigger AcmeHandler.setup_acme_client to make backend requests. An attacker could target cloud instance metadata or internal services from Lemur network context, potentially obtaining credentials available to the host. The advisory also identifies creator-equality authorization behavior that could preserve access to certificate key material after ownership or role changes, with insufficient export_private_key audit context to distinguish that access path. Together, the acme_url server-side request forgery and authorization weakness could expose cloud credentials and long-lived PKI private-key access. The fix adds ACME_DIRECTORY_HOST_ALLOWLIST validation and enriches key-export audit events with creator and current-owner context. This issue is fixed in version 1.9.2. | GCVE Database | ||
| Medium | 5.3 | EPSS 0.4% | CVE-2026-44202Org.openidentityplatform.openam:openam core: OpenAM Authenticated Server-Side Request Forgery (SSRF) via Medium5.3EPSS 0.4%GCVE DatabaseCVE-2026-44202 OpenAM, an open-source IAM platform, has a server-side request forgery (SSRF) vulnerability in its /sessionservice endpoint. Authenticated users can register URLs for session event notifications without sufficient restrictions, allowing outbound requests to attacker-controlled destinations. This may expose session-related data. The vulnerability affects versions prior to 16.1.1 and has a high severity score of 8.6. A fix is available in version 16.1.1. | GCVE Database | ||
| Medium | 6.1 | EPSS 0.4% | CVE-2026-56342AVideo · Server-Side Request Forgery (SSRF) Medium6.1EPSS 0.4%CVE Database V5CVE-2026-56342 AVideo versions up to 27.0 contain a server-side request forgery (SSRF) vulnerability in the plugin/Live/test.php component. Authenticated administrators can exploit this flaw by manipulating the statsURL parameter, which lacks proper SSRF validation, to access arbitrary URLs including internal network addresses and cloud metadata endpoints. This can lead to exposure of sensitive information such as IAM credentials and internal service data. EPSS 0.4%Vulnerability | CVE Database V5 | ||
| Medium | 6.8 | EPSS 0.4% | CVE-2026-48782pydantic-ai · Server-Side Request Forgery (SSRF) Medium6.8EPSS 0.4%CVE Database V5CVE-2026-48782 ## Summary When an application using Pydantic AI opts a URL into `force_download='allow-local'` (which disables the default block on private/internal IPs) **and runs on a network that routes the affected IPv6 transition forms (NAT64- or ISATAP-configured networks)**, the cloud-metadata blocklist could be bypassed by encoding the metadata IP in an IPv6 transition form that the previous fix did not decode — IPv4-compatible IPv6 (`::a.b.c.d`), the NAT64 RFC 8215 local-use prefix (`64:ff9b:1::/48`), operator-chosen NAT64 prefixes, or ISATAP. The IPv6 wrapper is then delivered to the underlying IPv4 metadata endpoint, exposing cloud IAM short-term credentials. **The bypass is exploitable only in environments whose network actually routes these forms** — NAT64-configured networks (IPv6-only or dual-stack-with-NAT64 deployments, including some Kubernetes setups) for the NAT64 variants, or networks with an ISATAP tunnel for ISATAP. A standard dual-stack cloud VM or container does not route them and is not affected in practice. The IPv4-compatible and Teredo variants are deprecated and addressed as defense-in-depth. This is an incomplete fix of [GHSA-cqp8-fcvh-x7r3](https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-cqp8-fcvh-x7r3) / [CVE-2026-46678](https://nvd.nist.gov/vuln/detail/CVE-2026-46678) (itself a follow-up to [CVE-2026-25580](https://nvd.nist.gov/vuln/detail/CVE-2026-25580)). The prior remediation decoded only IPv4-mapped IPv6, 6to4, and the NAT64 well-known prefix; the metadata guarantee did not hold for the remaining transition forms. ## Severity **MEDIUM** — `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N` = **6.8** Same impact metrics and narrow attack surface as the parent advisory (AC:H): exploitation requires the application to have opted into `allow-local` on a URL influenced by untrusted input, and the NAT64/ISATAP variants additionally require the deployment network to route those forms. **CWE-918**: Server-Side Request Forgery (SSRF) ## Affected Versions | Package | Vulnerable | Patched | |---|---|---| | `pydantic-ai` | `>= 1.56.0, < 1.102.0`; `>= 2.0.0b1, < 2.0.0b3` | `1.102.0`; `2.0.0b3` | | `pydantic-ai-slim` | `>= 1.56.0, < 1.102.0`; `>= 2.0.0b1, < 2.0.0b3` | `1.102.0`; `2.0.0b3` | These transition forms have not been decoded since SSRF protection was introduced in `1.56.0`. ## Who Is Affected Users are affected **only if** their application explicitly opts a `FileUrl` (`ImageUrl`, `AudioUrl`, `VideoUrl`, `DocumentUrl`) into `force_download='allow-local'` on a URL that is, or could be, influenced by untrusted input. Beyond that precondition, the affected encodings only reach a metadata endpoint in environments whose network actually routes them. The broadly-routable IPv4-mapped form was addressed in `1.99.0` (CVE-2026-46678); the additional forms addressed here require a **NAT64-configured network** (IPv6-only or dual-stack-with-NAT64 deployments, including some Kubernetes setups) for the NAT64 variants, or an **ISATAP tunnel** for the ISATAP variant. The IPv4-compatible and Teredo forms are deprecated and not routed by modern stacks; they are addressed as defense-in-depth. Most deployments on a standard dual-stack cloud VM or container are therefore not exploitable in practice, but the fix restores the "always blocked" guarantee for the environments that are. Users are **not** affected if they use any of the bundled integrations to ingest user input, because they do not propagate `force_download` from external data: - `Agent.to_web` / `clai web` - `VercelAIAdapter` - `AGUIAdapter` / `Agent.to_ag_ui` Applications that only download from developer-controlled URLs are not affected. ## Remediation Upgrade to `1.102.0` or later (or `2.0.0b3` or later on the 2.0 pre-release line). The cloud-metadata and private-IP blocklists now decode the embedded IPv4 of every standardized IPv6 transition form before evaluating it — IPv4-mapped, IPv4-compatible, 6to4, NAT64 across all prefix lengths (including the RFC 8215 local-use prefix and operator-chosen prefixes), ISATAP, and Teredo. The set of always-blocked cloud metadata/credential endpoints has also been expanded across providers. ## Workaround for Unpatched Versions Avoid passing `force_download='allow-local'` on any URL that could be influenced by untrusted input. If developers must, resolve the hostname themselves and validate the result against their own metadata blocklist — including IPv6 transition forms — before constructing the `FileUrl`. ## Credits Reported by [@SnailSploit](https://snailsploit.com). | CVE Database V5 | ||
| Medium | 6.1 | EPSS 0.2% | CVE-2026-50089Aqara IAM/SSO Gateway · Open Redirect Medium6.1EPSS 0.2%CVE Database V5CVE-2026-50089 CVE-2026-50089 is a medium severity vulnerability in the Aqara IAM/SSO Gateway that allows an open redirect to untrusted sites. This issue is classified as CWE-601 and can be exploited to facilitate phishing attacks by redirecting users to malicious URLs. The vulnerability requires no privileges and user interaction is needed to trigger the redirect. It impacts confidentiality and integrity but not availability. | CVE Database V5 | ||
| High | 8.2 | EPSS 0.2% | CVE-2026-50087Aqara IAM/SSO Gateway · Permissive cross-domain security policy with untrusted domains High8.2EPSS 0.2%CVE Database V5CVE-2026-50087 The Aqara IAM/SSO Gateway has a high-severity vulnerability (CVE-2026-50087) involving a permissive cross-domain security policy that allows untrusted domains to perform cross-origin requests. This vulnerability is categorized under CWE-942 and affects the gateway version dated 2026-04-20. It has a CVSS 3.1 score of 8.2, indicating a high impact on confidentiality with limited impact on integrity and no impact on availability. No official patch or remediation guidance is currently available. | CVE Database V5 | ||
| Critical | 9.1 | EPSS 0.4% | Critical9.1EPSS 0.4%CVE Database V5CVE-2026-50083 The Aqara IAM/SSO Gateway has a critical vulnerability due to the use of a hardcoded OAuth client credential (CWE-798). This flaw allows attackers to potentially compromise confidentiality and integrity without authentication or user interaction. The vulnerability has a CVSS score of 9.1 (critical). When combined with related vulnerabilities, it may enable a fully unauthenticated remote takeover of affected devices. No official patch or remediation guidance is currently available. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8695ea17273c804f1a58e6c0b877de280f7472622065964245deb85cc62dae20) The package declares a postinstall lifecycle hook (postinstall.js) that runs automatically on `npm install`. The script shells out via curl to the EC2 IMDSv2 metadata endpoint to obtain IAM role credentials, exports them, then iterates AWS Secrets Manager across multiple regions calling `aws secretsmanager list-secrets` and `get-secret-value`, and additionally dumps any process environment variable matching `FLAG|HTB|SECRET|AWS_`. The captured blob is chunked and HTTP PUT to a hardcoded bare-IP destination (http://154.57.164.71:30782) framed as a fake 'manifest' JSON. Execution is gated by an `isAppWorker()` check (hostname matches a 12-hex Docker-style ID and cwd contains `/app/node_modules`), which narrows the victim profile to containerized CI/build workers but does not change the nature of the attack. Additional behavior includes scanning /app for HackTheBox flag patterns (`/HTB\{[^}]+\}/`) and reading /app/src/main.rs, /app/main.rs, /app/flag.txt. This is unambiguous install-time credential theft plus remote exfiltration: any installer whose container matches the gate has IAM role credentials, secrets, and environment-variable secrets sent to attacker-controlled infrastructure. ## Source: ghsa-malware (d0ca45bd5ff9251df7ade64227231b9db2164ed9c61735808e83cb5626c3505a) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| High | 7.7 | EPSS 0.2% | CVE-2026-39910STACKIT IaaS API · Missing Authorization High7.7EPSS 0.2%CVE Database V5CVE-2026-39910 STACKIT IaaS API contains a missing authorization check in the PUT servers service-accounts endpoint. An authenticated, low-privileged attacker can attach an arbitrary service account to a virtual machine they control without validation of their permission to use it, then query the Instance Metadata Service (IMDS) to retrieve an OAuth2 token for that service account and act with its privileges. The impact is confined to the attacker’s own project. The STACKIT Identity Provider enforces strict project matching between the target VM and the requested service account during token impersonation, so cross-project and cross-organization exploitation is not possible. Any further access is bounded by the IAM roles already assigned to the targeted service account. | CVE Database V5 |
Page 6 of 8 · 1 duplicate CVE record merged