---METADATA---
VENDOR: AWS
PRODUCT: Ops Wheel
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
AWS Ops Wheel is vulnerable to an attribute modification flaw in Cognito User Pool configuration, allowing authenticated users to escalate their privileges to deployment administrator.

Executive Summary:
An authenticated privilege escalation vulnerability in AWS Ops Wheel allows remote users to gain deployment administrator access by manipulating Cognito User Pool attributes.

Vulnerability Details

CVE-ID: CVE-2026-6912

Affected Software: AWS Ops Wheel

Affected Versions: See vendor advisory for affected versions (Fixed in PR #165)

Vulnerability: The vulnerability involves improper control of dynamically-determined object attributes. An authenticated user can leverage a crafted UpdateUserAttributes API call to modify the custom:deployment_admin attribute, effectively granting themselves unauthorized administrative control over user accounts.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a significant threat to cloud administrative integrity. Successful exploitation leads to full unauthorized administrative access, allowing an attacker to manipulate user accounts, access sensitive cloud resources, and potentially compromise the entire deployment environment.

Remediation Plan

Immediate Action: Update AWS Ops Wheel to the version containing the fix for PR #165 or apply the vendor-recommended security patch immediately.

Proactive Monitoring: Audit CloudTrail and Cognito logs for any UpdateUserAttributes API calls that modify custom attributes, specifically looking for unauthorized changes to deployment_admin flags.

Compensating Controls: Implement strict IAM policies to restrict the permissions of standard users, preventing them from accessing or modifying sensitive Cognito user attributes.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 26, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Privilege escalation vulnerabilities are critical in cloud environments. Administrators must audit current Cognito configurations and apply the necessary updates to Ops Wheel to prevent unauthorized administrative takeover.

---METADATA---
VENDOR: AWS
PRODUCT: Ops Wheel
AFFECTED_VERSIONS: See vendor advisory
CONFIDENCE: high
MISSING: versions
---END_METADATA---

Description Summary:
A missing JWT signature verification in AWS Ops Wheel allows unauthenticated attackers to forge tokens and gain administrative access to the application.

Executive Summary:
AWS Ops Wheel is affected by a critical authentication bypass vulnerability that permits unauthenticated attackers to forge JWT tokens and gain full administrative control.

Vulnerability Details

CVE-ID: CVE-2026-6911

Affected Software: AWS Ops Wheel

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability stems from a complete lack of JWT signature verification. An unauthenticated attacker can craft and submit arbitrary JWTs to the API Gateway to impersonate administrative users, bypassing all authentication mechanisms.

Business Impact

This flaw grants an attacker full administrative control over the application, including the ability to manipulate data across all tenants and manage user accounts in Cognito. The CVSS score of 9.8 reflects the extreme risk of unauthorized access and potential for massive data breach or service destruction. Organizations relying on this tool for infrastructure management face a critical threat to their entire cloud deployment.

Remediation Plan

Immediate Action: Redeploy the application using the updated repository provided by the vendor and ensure all forked or derivative codebases incorporate the security patch.

Proactive Monitoring: Audit logs for suspicious administrative actions or unauthorized API requests utilizing forged tokens.

Compensating Controls: Restrict access to the API Gateway endpoint via IP whitelisting or mutual TLS until the patch is successfully deployed.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Apr 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this flaw cannot be overstated; it is a complete authentication bypass. Administrators must treat this as an emergency update, as the flaw allows for unauthenticated access to the core administrative functions of the deployment.

---METADATA---
VENDOR: ISC
PRODUCT: BIND 9
AFFECTED_VERSIONS: 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, 9.20.9-S1 through 9.20.22-S1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Multiple flaws in the BIND 9 named component allow for improper input validation and out-of-bounds reads when handling non-Internet DNS message classes.

Executive Summary:
A critical vulnerability in the ISC BIND 9 DNS server software allows for potential service disruption or crashes due to improper handling of specific DNS message classes.

Vulnerability Details

CVE-ID: CVE-2026-5946

Affected Software: ISC BIND 9

Affected Versions: 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and associated Subscription Edition (S1) versions.

Vulnerability: This vulnerability involves improper input validation (CWE-20), out-of-bounds read (CWE-125), and reachable assertions (CWE-617) within named. It can be triggered by unauthenticated remote attackers sending specially crafted DNS queries containing non-standard classes like CHAOS, HESIOD, or meta-classes.

Business Impact

Successful exploitation of this flaw can lead to a denial-of-service (DoS) condition, crashing the DNS service and rendering name resolution unavailable for dependent infrastructure. Given the CVSS score of 7.5, this poses a significant risk to network availability and business continuity.

Remediation Plan

Immediate Action: Upgrade to the patched releases: 9.18.49, 9.20.23, 9.21.22, 9.18.49-S1, or 9.20.23-S1.

Proactive Monitoring: Monitor named service logs for frequent restarts or crash reports coinciding with unusual DNS query traffic patterns.

Compensating Controls: Implement firewall rules to drop non-standard DNS query traffic if your environment does not require support for CHAOS or HESIOD classes.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 22, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations running BIND 9 must prioritize patching to the versions listed above. Given the potential for automated exploitation, failure to address this flaw could lead to significant infrastructure outages.

---METADATA---
VENDOR: AWS
PRODUCT: aws-mcp-server
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
The aws-mcp-server is vulnerable to remote code execution via AWS CLI command injection, allowing attackers to execute arbitrary system commands without authentication.

Executive Summary:
An unauthenticated remote code execution vulnerability in aws-mcp-server allows attackers to execute arbitrary commands, creating a critical security risk.

Vulnerability Details

CVE-ID: CVE-2026-5059

Affected Software: AWS aws-mcp-server

Affected Versions: See vendor advisory

Vulnerability: This is a command injection vulnerability occurring within the handling of the allowed commands list. The application fails to validate user-supplied strings, allowing unauthenticated remote attackers to trigger arbitrary system calls.

Business Impact

With a CVSS score of 9.8, this vulnerability is critical. Successful exploitation allows an attacker to run code with the privileges of the MCP server, leading to potential data theft, infrastructure disruption, and unauthorized access to cloud resources.

Remediation Plan

Immediate Action: Update all aws-mcp-server installations to the latest vendor-supplied version immediately.

Proactive Monitoring: Monitor server logs for unauthorized command execution or anomalous process activity linked to the MCP service.

Compensating Controls: Use network segmentation and restrictive IAM policies to limit the blast radius should the MCP server be compromised.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of April 11, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Due to the critical severity of this remote code execution flaw, immediate patching is required. Security teams should verify the version of all deployed instances and apply updates as a top priority.

---METADATA---
VENDOR: AWS
PRODUCT: aws-mcp-server
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
The aws-mcp-server is vulnerable to remote code execution via command injection due to improper validation of user-supplied input in the allowed commands list.

Executive Summary:
An unauthenticated remote code execution vulnerability in aws-mcp-server allows attackers to execute arbitrary system commands, posing a critical risk to server integrity.

Vulnerability Details

CVE-ID: CVE-2026-5058

Affected Software: AWS aws-mcp-server

Affected Versions: See vendor advisory

Vulnerability: This is a command injection vulnerability where the application fails to sanitize input before passing it to a system call. The vulnerability is exploitable by unauthenticated remote attackers.

Business Impact

With a CVSS score of 9.8, this vulnerability represents a critical risk. Successful exploitation grants an attacker the ability to execute arbitrary code within the context of the MCP server, potentially leading to full system compromise, data exfiltration, and unauthorized lateral movement within the AWS environment.

Remediation Plan

Immediate Action: Apply the latest security patches or updates provided by the vendor to the aws-mcp-server installations immediately.

Proactive Monitoring: Review system and application logs for unusual process execution or shell command invocations originating from the MCP service.

Compensating Controls: Implement strict network ingress filtering to restrict access to the MCP server to known, trusted IP addresses, effectively limiting the attack surface.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of April 11, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical CVSS severity, organizations should prioritize patching affected aws-mcp-server instances. Failure to remediate this vulnerability may result in total system compromise.

---METADATA---
VENDOR: enesgkky
PRODUCT: Pulpy
AFFECTED_VERSIONS: < 0.1.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Pulpy desktop application packager contains an incomplete path blocklist in its filesystem API, allowing packaged web applications to access sensitive files in the user's home directory.

Executive Summary:
A critical path traversal vulnerability in Pulpy allows packaged web applications to read and write sensitive user files, including SSH keys and cloud credentials.

Vulnerability Details

CVE-ID: CVE-2026-44225

Affected Software: enesgkky Pulpy

Affected Versions: < 0.1.1

Vulnerability: This is an improper access control and path traversal vulnerability where the validateFsPath() function fails to properly sandbox the pulpy.fs JavaScript API. An attacker-controlled web application can bypass the blocklist to access restricted files such as ~/.ssh/id_rsa or ~/.aws/credentials.

Business Impact

Exploitation allows for the theft of credentials, cryptographic keys, and sensitive local data, leading to a total compromise of the user's local workstation and potential lateral movement into cloud environments. The high CVSS score of 9.3 reflects the severity of this unauthorized access to highly sensitive system files.

Remediation Plan

Immediate Action: Update all applications packaged with Pulpy to version 0.1.1 or later and rebuild the application bundles.

Proactive Monitoring: Scan for unauthorized file access attempts or anomalous read/write activity on sensitive system configuration files.

Compensating Controls: Implement endpoint protection solutions to monitor and block unauthorized processes from accessing sensitive directories like ~/.ssh or ~/.aws.

Exploitation Status

Public Exploit Available: Yes (Proof of Concept)

Analyst Notes: As of May 12, 2026, while there is no public information indicating widespread active exploitation, a proof-of-concept exists. The potential for exploitation is high.

Analyst Recommendation

The risk of credential theft via this vulnerability is significant for developers and users of applications packaged with Pulpy. It is imperative to update the packager and redistribute affected software immediately to prevent local data compromise.

---METADATA---
VENDOR: oxyno-zeta
PRODUCT: s3-proxy
AFFECTED_VERSIONS: Prior to 5.0.0
---END_METADATA---

Description Summary:
The oxyno-zeta s3-proxy contains an authentication bypass vulnerability due to inconsistent path interpretation, allowing unauthorized S3 operations.

Executive Summary:
An unauthenticated attacker can perform unauthorized read, write, or delete operations on protected S3 buckets by exploiting a path-based authentication bypass in s3-proxy.

Vulnerability Details

CVE-ID: CVE-2026-42882

Affected Software: oxyno-zeta s3-proxy

Affected Versions: Prior to 5.0.0

Vulnerability: This is an authentication bypass vulnerability caused by a mismatch between how the authentication middleware and the bucket handler resolve URL paths. An unauthenticated attacker can use path traversal or encoded characters to access restricted S3 namespaces.

Business Impact

This flaw allows for unauthorized data modification or exfiltration from S3 storage, directly threatening data integrity and confidentiality. Given the 9.4 CVSS score, this is a major security failure that could lead to the total exposure of sensitive object storage.

Remediation Plan

Immediate Action: Upgrade to s3-proxy version 5.0.0 or later.

Proactive Monitoring: Review S3 access logs for unexpected access requests or operations performed on sensitive buckets from unauthorized sources.

Compensating Controls: Implement bucket-level policies and IAM restrictions that limit the IP addresses or roles authorized to access the storage backend.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 11, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators should update s3-proxy immediately to version 5.0.0. Furthermore, ensure that the principle of least privilege is applied to all IAM entities interacting with the affected S3 buckets.

---METADATA---
VENDOR: FireFighter
PRODUCT: FireFighter Incident Management
AFFECTED_VERSIONS: Prior to 0.0.54
---END_METADATA---

Description Summary:
FireFighter incident management application contains an unauthenticated SSRF vulnerability that can lead to the theft of AWS IAM credentials.

Executive Summary:
An unauthenticated attacker can exploit an SSRF vulnerability in the FireFighter API to exfiltrate sensitive AWS IAM credentials from the underlying infrastructure.

Vulnerability Details

CVE-ID: CVE-2026-42864

Affected Software: FireFighter Incident Management

Affected Versions: Prior to 0.0.54

Vulnerability: This is a Server-Side Request Forgery (SSRF) vulnerability in the /api/v2/firefighter/raid/jira_bot endpoint. An unauthenticated attacker can force the application to fetch arbitrary URLs, which, in cloud environments without IMDSv2, leads to the exposure of temporary AWS credentials.

Business Impact

The impact of this vulnerability is critical, as it provides an attacker with direct access to cloud resources via stolen IAM credentials. With a CVSS score of 9.9, this vulnerability can lead to full compromise of the cloud environment and any data residing within.

Remediation Plan

Immediate Action: Update FireFighter to version 0.0.54 or later.

Proactive Monitoring: Monitor AWS CloudTrail logs for unauthorized API calls originating from the application's IAM role.

Compensating Controls: Enforce IMDSv2 (Instance Metadata Service Version 2) on all EC2/EKS instances to require session-oriented authentication for metadata requests.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 11, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability is extremely severe. Immediate patching is required, and administrators must simultaneously verify that IMDSv2 is strictly enforced across their cloud infrastructure to prevent credential exfiltration.

---METADATA---
VENDOR: Plunk
PRODUCT: Plunk (Email platform)
AFFECTED_VERSIONS: Prior to 0.9.0
---END_METADATA---

Description Summary:
The Plunk email platform fails to verify SNS signatures, allowing unauthenticated attackers to forge webhook requests.

Executive Summary:
A critical authentication bypass in the Plunk platform allows unauthenticated attackers to spoof AWS SNS events and manipulate email delivery workflows.

Vulnerability Details

CVE-ID: CVE-2026-42193

Affected Software: Plunk

Affected Versions: Prior to 0.9.0

Vulnerability: The /webhooks/sns endpoint does not validate the Amazon SNS signature, certificate, or topic ARN, allowing an attacker to submit forged requests.

Business Impact

This vulnerability allows attackers to manipulate email metrics, unsubscribe users, and potentially exhaust billing credits. With a CVSS score of 9.1, it represents a significant risk to operational integrity and potential financial loss for businesses relying on the platform.

Remediation Plan

Immediate Action: Update Plunk to version 0.9.0 or later to enable proper signature verification.

Proactive Monitoring: Review application logs for unexpected webhook activity or high volumes of SNS events that do not correlate with legitimate traffic.

Compensating Controls: Use a Web Application Firewall (WAF) to restrict access to the /webhooks/sns endpoint to only traffic originating from verified AWS IP ranges.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 8, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The inability to verify the authenticity of webhook requests makes this a high-priority update. Organizations should ensure their instance is patched to prevent unauthorized manipulation of email operations.

---METADATA---
VENDOR: AWS
PRODUCT: excel-mcp-server
AFFECTED_VERSIONS: Up to and including 0.1.7
---END_METADATA---

Description Summary:
A path traversal vulnerability in excel-mcp-server allows unauthenticated remote attackers to read, write, and overwrite arbitrary files on the host filesystem.

Executive Summary:
An unauthenticated path traversal vulnerability in the AWS excel-mcp-server enables remote attackers to achieve full filesystem access, posing a critical threat to host integrity.

Vulnerability Details

CVE-ID: CVE-2026-40576

Affected Software: AWS excel-mcp-server

Affected Versions: Up to and including 0.1.7

Vulnerability: The application fails to properly validate file paths within its tool handlers, allowing an unauthenticated attacker to escape the designated directory and perform arbitrary file operations.

Business Impact

Successful exploitation allows an unauthenticated attacker to read sensitive configuration files, modify application logic, or overwrite system files, leading to a complete compromise of the host environment. Given the CVSS score of 9.4, this vulnerability represents an extreme risk to data confidentiality, integrity, and availability.

Remediation Plan

Immediate Action: Upgrade to version 0.1.8 or later immediately to resolve the path validation flaws.

Proactive Monitoring: Inspect server logs for unusual file access patterns or attempts to access system directories outside the intended EXCEL_FILES_PATH.

Compensating Controls: If immediate patching is not possible, restrict network access to the MCP server transport interface using firewall rules or ACLs to ensure only authorized clients can reach the service.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Apr 21, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this flaw necessitates immediate attention. Organizations utilizing the excel-mcp-server in SSE or Streamable-HTTP mode should prioritize the transition to version 0.1.8 to prevent unauthorized remote file manipulation.

---METADATA---
VENDOR: Axios
PRODUCT: Axios
AFFECTED_VERSIONS: Prior to 1.15.0
---END_METADATA---

Description Summary:
Axios is vulnerable to a prototype pollution attack chain that can be escalated to remote code execution or AWS IMDSv2 bypass.

Executive Summary:
A critical vulnerability in the Axios library allows for prototype pollution to be escalated into remote code execution or full cloud environment compromise.

Vulnerability Details

CVE-ID: CVE-2026-40175

Affected Software: Axios

Affected Versions: Prior to 1.15.0

Vulnerability: This vulnerability involves a "Gadget" attack chain where prototype pollution is leveraged to achieve remote code execution or bypass AWS IMDSv2 protections. The vulnerability is accessible to external attackers through the HTTP client's processing of malicious data.

Business Impact

With a CVSS score of 10.0, this is a maximum-severity flaw. The impact ranges from full server takeover to the compromise of cloud infrastructure, potentially allowing attackers to escalate privileges and access sensitive cloud metadata, leading to widespread data breaches.

Remediation Plan

Immediate Action: Update the Axios library to version 1.15.0 or later across all applications and dependencies.

Proactive Monitoring: Utilize Software Composition Analysis (SCA) tools to identify and track the usage of vulnerable Axios versions throughout the development lifecycle.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block malicious payloads associated with prototype pollution techniques.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of April 10, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this vulnerability necessitates an immediate update. Development teams must ensure that all instances of Axios are patched to the secure version to prevent potential cloud-level compromises.

---METADATA---
VENDOR: Anthropic
PRODUCT: Claude Code CLI and Claude Agent SDK
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
Anthropic Claude CLI and SDK are vulnerable to OS command injection via unvalidated authentication helper configuration parameters, allowing arbitrary command execution.

Executive Summary:
An OS command injection vulnerability in Anthropic Claude tools allows attackers to execute arbitrary code with the privileges of the automation environment, posing a critical risk of system compromise.

Vulnerability Details

CVE-ID: CVE-2026-35022

Affected Software: Anthropic Claude Code CLI and Claude Agent SDK

Affected Versions: See vendor advisory

Vulnerability: The vulnerability exists in the authentication helper execution logic, which uses shell=true without input validation. An attacker who can influence authentication settings can inject shell metacharacters into parameters to execute commands with the privileges of the active user.

Business Impact

A successful exploit allows for full command execution, leading to potential credential theft, environment variable exfiltration, and complete compromise of the host machine or automation pipeline. With a CVSS score of 9.8, this vulnerability represents a critical threat to data confidentiality and integrity.

Remediation Plan

Immediate Action: Update the Claude Code CLI and Claude Agent SDK to the latest available versions immediately.

Proactive Monitoring: Audit environment configurations and logs for unexpected shell invocations or unauthorized modifications to authentication helper parameters.

Compensating Controls: Implement strict input validation and access controls for any configuration files or environment variables that influence authentication helper execution.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Apr 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this flaw necessitates immediate attention. Organizations utilizing Anthropic automation tools must verify their current versioning and apply patches as soon as they are made available by the vendor to prevent unauthorized command execution and environment compromise.

---METADATA---
VENDOR: ParisNeo
PRODUCT: lollms-webui
AFFECTED_VERSIONS: All versions prior to publication
---END_METADATA---

Description Summary:
A critical Server-Side Request Forgery (SSRF) in lollms-webui allows unauthenticated attackers to force arbitrary GET requests, potentially exfiltrating sensitive cloud metadata and IAM tokens.

Executive Summary:
An unauthenticated SSRF vulnerability in lollms-webui poses a critical risk to cloud infrastructure by allowing attackers to exfiltrate sensitive IAM credentials and scan internal networks.

Vulnerability Details

CVE-ID: CVE-2026-33340

Affected Software: ParisNeo lollms-webui

Affected Versions: All known existing versions

Vulnerability: This vulnerability is a Server-Side Request Forgery (SSRF) residing in the @router.post("/api/proxy") endpoint. It allows an unauthenticated remote attacker to coerce the server into performing arbitrary GET requests against internal or external resources.

Business Impact

A successful exploit could lead to the total compromise of cloud-hosted environments through the exfiltration of AWS or GCP IAM metadata tokens. Furthermore, attackers can use the vulnerable instance as a pivot point to map and attack internal network services that are not exposed to the public internet. The CVSS score of 9.1 reflects the critical nature of this flaw and the high potential for unauthorized access to sensitive infrastructure.

Remediation Plan

Immediate Action: As no official patch is currently available, administrators should immediately disable public access to the lollms-webui interface or implement strict IP whitelisting.

Proactive Monitoring: Review web server access logs for unusual POST requests directed at the /api/proxy endpoint and monitor outbound traffic for connections to cloud metadata services (e.g., 169.254.169.254).

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules specifically designed to block requests containing internal IP addresses or metadata service URLs in the proxy payload.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Mar 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and the increasing popularity of LLM interfaces, the potential for exploitation is high.

Analyst Recommendation

The severity of this SSRF vulnerability cannot be overstated, particularly for deployments in cloud environments. Organizations should consider the software "at-risk" until a formal patch is released. Immediate network-level isolation is the only effective way to mitigate the risk of credential theft and lateral movement at this time.

---METADATA---
VENDOR: Plunk
PRODUCT: Plunk
AFFECTED_VERSIONS: Prior to 0.7.0
---END_METADATA---

Description Summary:
Plunk contains an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in its SNS webhook handler, allowing attackers to make arbitrary outbound GET requests.

Executive Summary:
An unauthenticated SSRF vulnerability in Plunk allows attackers to probe internal network resources and potentially exfiltrate sensitive cloud metadata.

Vulnerability Details

CVE-ID: CVE-2026-32096

Affected Software: Plunk (Email Platform)

Affected Versions: Prior to 0.7.0

Vulnerability: A flaw in the Amazon Simple Notification Service (SNS) webhook handler allows an unauthenticated attacker to send crafted requests. This forces the server to initiate arbitrary outbound HTTP GET requests to any host, including internal services or cloud metadata endpoints (e.g., IMDS).

Business Impact

A successful SSRF attack can lead to the compromise of internal services not exposed to the internet and the theft of sensitive environment variables or cloud IAM credentials. The CVSS score of 9.3 highlights the significant risk to the confidentiality and security of the underlying AWS infrastructure.

Remediation Plan

Immediate Action: Update the Plunk platform to version 0.7.0 or higher immediately.

Proactive Monitoring: Monitor outbound network logs for unusual GET requests originating from the Plunk server, particularly those targeting internal IP ranges or the 169.254.169.254 metadata address.

Compensating Controls: Implement egress filtering to restrict the Plunk server's ability to communicate with internal network segments or sensitive cloud metadata services.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Mar 11, 2026, there is no public information indicating active exploitation. SSRF vulnerabilities are frequently used in cloud environments to escalate privileges by targeting instance metadata services.

Analyst Recommendation

The ability for an unauthenticated attacker to trigger outbound requests is a high-risk scenario. Administrators must apply the version 0.7.0 patch immediately and verify that the server's network permissions follow the principle of least privilege.

---METADATA---
VENDOR: LibreChat
PRODUCT: LibreChat
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A high-severity vulnerability has been identified in LibreChat, a ChatGPT clone, which may lead to unauthorized access or system compromise.

Executive Summary:
LibreChat is affected by a high-severity security flaw that could compromise the confidentiality and integrity of the AI chat platform.

Vulnerability Details

CVE-ID: CVE-2026-31943

Affected Software: LibreChat

Affected Versions: See vendor advisory for affected versions

Vulnerability: While the specific technical vector is not detailed in the summary, the high CVSS score of 8.5 suggests a significant flaw, likely involving improper access control or input validation within the LibreChat application.

Business Impact

A successful exploit could allow attackers to access private chat histories, manipulate AI responses, or gain unauthorized access to the application's underlying infrastructure. Given the CVSS score of 8.5, this vulnerability poses a substantial risk to user privacy and organizational data security, potentially leading to regulatory non-compliance.

Remediation Plan

Immediate Action: Apply the latest security updates provided by the LibreChat maintainers immediately to close the identified security gap.

Proactive Monitoring: Review application logs for unusual API calls or unauthorized attempts to access user sessions and administrative settings.

Compensating Controls: Implement strong authentication mechanisms, such as Multi-Factor Authentication (MFA), and use a Web Application Firewall to monitor incoming traffic for malicious patterns.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 28, 2026, there is no public information indicating active exploitation of this vulnerability. Users should remain vigilant as ChatGPT clones are increasingly targeted by threat actors seeking to harvest credentials or session tokens.

Analyst Recommendation

The high severity of this vulnerability requires immediate attention. Organizations deploying LibreChat should verify their current version and update to the latest patched release to ensure the continued security of their AI communications and data.

---METADATA---
VENDOR: Budibase
PRODUCT: Budibase Cloud (SaaS)
AFFECTED_VERSIONS: Prior to version 3.30.4
---END_METADATA---

Description Summary:
Budibase Cloud suffers from an unsafe eval() vulnerability in its view filtering, allowing authenticated users to execute arbitrary JavaScript and access sensitive environment secrets.

Executive Summary:
An authenticated remote code execution vulnerability in Budibase Cloud allows users to compromise the server environment and extract highly sensitive administrative credentials.

Vulnerability Details

CVE-ID: CVE-2026-27702

Affected Software: Budibase Budibase Cloud (SaaS)

Affected Versions: Prior to version 3.30.4

Vulnerability: This flaw involves an unsafe eval() call within the inMemoryView.ts component where user-controlled input is processed without sanitization. Any authenticated user, including those on free tier accounts, can trigger this to execute arbitrary code with the privileges of the application service.

Business Impact

A successful exploit grants an attacker access to the pod's environment variables, which include critical secrets such as INTERNAL_API_KEY, JWT_SECRET, and AWS keys. This leads to total database compromise, the ability to enumerate all tenant databases, and unauthorized access to sensitive user records and email addresses. With a CVSS score of 9.9, this represents a critical risk to data confidentiality and platform integrity.

Remediation Plan

Immediate Action: Budibase Cloud users must ensure they are using version 3.30.4 or later; as this is a SaaS product, confirm with the vendor that the patch is applied.

Proactive Monitoring: Security teams should review access logs for unusual view filtering activity and rotate any credentials or API keys that may have been exposed in the environment.

Compensating Controls: Implement strict egress filtering on the application environment to prevent the exfiltration of environment variables to external attacker-controlled servers.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Feb 25, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and the sensitivity of the exposed secrets, the potential for exploitation is extremely high.

Analyst Recommendation

The severity of this RCE vulnerability cannot be overstated, as it exposes the foundational secrets of the Budibase Cloud infrastructure. Organizations must verify that their instances are running the patched version and immediately rotate all administrative secrets to mitigate the risk of persistent access by a malicious actor.

---METADATA---
VENDOR: Hono
PRODUCT: Hono
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
The Hono web application framework is affected by a high-severity vulnerability that could impact any JavaScript runtime environment it supports.

Executive Summary:
A high-severity vulnerability in the Hono web framework poses a significant risk to applications deployed across various JavaScript runtimes, requiring urgent updates.

Vulnerability Details

CVE-ID: CVE-2026-27700

Affected Software: Hono Hono

Affected Versions: See vendor advisory for affected versions

Vulnerability: Hono is a web framework supporting multiple JavaScript runtimes. This vulnerability, carrying a CVSS score of 8.2, indicates a significant flaw in the framework's handling of web requests or runtime execution, though specific technical details are currently withheld by the vendor.

Business Impact

Applications built on the Hono framework may be susceptible to exploitation, leading to unauthorized data access or service disruption. Because Hono is runtime-agnostic, the vulnerability could manifest across diverse cloud and edge computing environments. The High severity rating reflects the potential for widespread impact across the framework's user base.

Remediation Plan

Immediate Action: Developers should update the Hono framework to the latest version in their project dependencies and redeploy affected applications.

Proactive Monitoring: Monitor application logs for anomalous request patterns or runtime errors that could indicate attempted exploitation of the framework.

Compensating Controls: Utilize a Web Application Firewall (WAF) to filter incoming traffic and provide an additional layer of protection while updates are being deployed.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 26, 2026, there is no public information indicating active exploitation of this vulnerability. The lack of public exploit code provides a window for organizations to patch before widespread attacks occur.

Analyst Recommendation

The Hono framework is a critical component for many modern web applications. To maintain a strong security posture, it is essential to apply the latest security updates immediately and verify the integrity of application deployments.

---METADATA---
VENDOR: Tandoor Recipes
PRODUCT: Tandoor Recipes
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
Tandoor Recipes, a meal management application, contains a high-severity vulnerability that could lead to unauthorized access or data compromise.

Executive Summary:
Tandoor Recipes is affected by a high-severity security vulnerability that poses a significant risk to the confidentiality and integrity of user data.

Vulnerability Details

CVE-ID: CVE-2026-25991

Affected Software: Tandoor Recipes

Affected Versions: See vendor advisory for affected versions

Vulnerability: While specific technical details of the flaw class are not fully disclosed in the initial summary, the CVSS score of 7.7 indicates a high-severity issue that likely involves unauthorized access or data manipulation within the recipe management platform.

Business Impact

A successful exploit could allow an attacker to access private user data, modify meal plans, or disrupt the availability of the application. For organizations or individuals relying on this platform for data management, this represents a significant breach of privacy and operational reliability.

Remediation Plan

Immediate Action: Apply the latest security updates provided by the Tandoor Recipes maintainers immediately to mitigate the identified risks.

Proactive Monitoring: Review application access logs for any unauthorized login attempts or unusual data modification patterns.

Compensating Controls: Ensure the application is behind a reverse proxy with strong authentication and limit exposure to the public internet where possible.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 14, 2026, there is no public information indicating active exploitation. The high CVSS score suggests that the vulnerability is serious and warrants immediate attention.

Analyst Recommendation

Security teams should treat this as a high-priority update. Promptly applying the vendor-supplied patches is the most effective way to protect the application environment from potential exploitation.

---METADATA---
VENDOR: OpenAEV
PRODUCT: OpenAEV
AFFECTED_VERSIONS: 1.0.0 through 2.0.12
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
OpenAEV contains critical password reset vulnerabilities, including indefinite token validity and weak entropy, allowing unauthenticated remote attackers to perform full account takeovers.

Executive Summary:
An unauthenticated account takeover vulnerability in OpenAEV, stemming from flawed password reset logic, enables attackers to compromise any user account, including administrative accounts.

Vulnerability Details

CVE-ID: CVE-2026-24467

Affected Software: OpenAEV OpenAEV

Affected Versions: 1.0.0 through 2.0.12

Vulnerability: The platform suffers from non-expiring password reset tokens and insufficient token complexity, enabling an unauthenticated attacker to brute-force tokens and reset any user's password. This flaw allows for reliable, scalable account takeover across the entire platform.

Business Impact

This vulnerability carries a CVSS score of 9.0, reflecting its potential for total platform compromise. Successful exploitation grants attackers the ability to access sensitive findings, modify simulation payloads, and compromise all hosts managed by the platform agents, leading to massive data breaches and loss of control over adversary simulation infrastructure.

Remediation Plan

Immediate Action: Upgrade all OpenAEV instances to version 2.0.13 immediately to resolve the password reset logic flaws.

Proactive Monitoring: Monitor authentication logs for high volumes of password reset requests or failed attempts, which may indicate automated brute-force activity against the reset mechanism.

Compensating Controls: Disable public access to the password reset endpoint if possible, or implement rate limiting and account lockout policies to thwart brute-force attempts.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Apr 20, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability is highly critical due to the lack of required authentication and the ease of mass account takeover. Administrators must treat this as a high-priority patching task and ensure all instances are updated to version 2.0.13 to restore the integrity of the authentication process.

---METADATA---
VENDOR: AWS
PRODUCT: Application Load Balancer
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
AWS Application Load Balancers with AWS WAF enabled may inconsistently inspect HTTP/2 request bodies, potentially allowing attackers to bypass WAF security rules via fragmented request frames.

Executive Summary:
A critical security bypass vulnerability in AWS Application Load Balancer allows attackers to evade WAF inspection by fragmenting HTTP/2 request bodies, necessitating a configuration change.

Vulnerability Details

CVE-ID: CVE-2026-13763

Affected Software: AWS Application Load Balancer

Affected Versions: See vendor advisory

Vulnerability: The issue arises from an inconsistent interpretation of HTTP/2 requests when AWS WAF is active. An unauthenticated attacker can exploit this by crafting HTTP/2 requests that fragment the body across multiple frames, causing the WAF to inspect only a partial body and effectively bypassing configured security policies.

Business Impact

With a CVSS score of 9.8, this vulnerability represents a significant failure in the security perimeter provided by AWS WAF. Attackers can leverage this bypass to deliver malicious payloads that would otherwise be blocked, leading to potential SQL injection, cross-site scripting, or other application-level attacks that threaten data integrity and system availability.

Remediation Plan

Immediate Action: Update the target group configuration in the AWS console to enable the "Inspect after sufficient data" attribute for all ALB target groups using HTTP/2.

Proactive Monitoring: Monitor WAF logs for unexpected spikes in traffic or requests that appear to be malformed or abnormally fragmented, as these may indicate evasion attempts.

Compensating Controls: If immediate configuration changes are not possible, consider restricting HTTP/2 traffic at the load balancer level where business requirements permit.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Jun 29, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical CVSS score, all users of AWS Application Load Balancer with WAF integration must verify their target group settings immediately. Enabling "Inspect after sufficient data" is the mandatory requirement to ensure the WAF correctly processes fragmented HTTP/2 request bodies and maintains the integrity of the security perimeter.

---METADATA---
VENDOR: AWS
PRODUCT: Language Servers for AWS
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A missing symlink validation vulnerability in Language Servers for AWS allows for arbitrary file writes outside of the intended workspace trust boundary.

Executive Summary:
Language Servers for AWS are susceptible to an arbitrary file write vulnerability that could allow an attacker to escape the workspace boundary and modify system files.

Vulnerability Details

CVE-ID: CVE-2026-12958

Affected Software: AWS Language Servers for AWS

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability stems from a failure to properly validate symbolic links. An attacker could exploit this to perform arbitrary file writes outside the designated workspace, potentially leading to unauthorized code execution or system configuration changes.

Business Impact

This vulnerability poses a severe risk to development environments. With a CVSS score of 7.8, the ability to write files outside of a trust boundary can be leveraged to gain elevated privileges or inject malicious code into the development pipeline, potentially resulting in downstream supply chain compromise.

Remediation Plan

Immediate Action: Apply the vendor-provided patch immediately to address the symlink validation logic.

Proactive Monitoring: Monitor for unusual file system activity, specifically writes occurring in directories outside of the defined project workspace.

Compensating Controls: Run the development environment with the principle of least privilege, ensuring the process has minimal write access to the underlying host operating system.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Arbitrary file write vulnerabilities in developer tooling are dangerous as they can lead to full system compromise of build servers. We strongly advise updating the affected AWS Language Servers immediately to mitigate the risk of unauthorized workspace escape and subsequent system manipulation.

---METADATA---
VENDOR: ASTPP
PRODUCT: Open Source Smart VoIP Billing Solution
AFFECTED_VERSIONS: 4.0.1
---END_METADATA---

Description Summary:
ASTPP 4.0.1 is vulnerable to XSS and command injection in SIP and plugin management interfaces, allowing attackers to hijack sessions and execute code with root permissions.

Executive Summary:
ASTPP 4.0.1 contains multiple critical flaws that enable attackers to gain root-level access and hijack administrator sessions through command injection and XSS.

Vulnerability Details

CVE-ID: CVE-2020-37153

Affected Software: ASTPP (Open Source Smart VoIP Billing Solution)

Affected Versions: 4.0.1

Vulnerability: The application suffers from multiple flaws including cross-site scripting (XSS) and command injection within the SIP device configuration and plugin management modules. Attackers can leverage these to inject system commands or manipulate cron tasks to achieve root-level code execution.

Business Impact

The compromise of a VoIP billing solution can lead to massive financial fraud, interception of sensitive communication data, and total system takeover. The CVSS score of 9.8 highlights the critical nature of these flaws, as they can lead to full administrative compromise and persistent access via cron manipulation.

Remediation Plan

Immediate Action: Upgrade ASTPP installations to the latest stable version where these vulnerabilities have been addressed.

Proactive Monitoring: Monitor system cron jobs for unauthorized changes and audit administrator session logs for suspicious activity or session hijacking indicators.

Compensating Controls: Use a WAF to filter malicious input in SIP configuration fields and enforce strict IP whitelisting for the management interface.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Feb 11, 2026, there is no public information indicating active exploitation. This is a late disclosure of a 2020 vulnerability, suggesting that legacy systems may still be at risk.

Analyst Recommendation

Given the potential for root-level access and the sensitive nature of VoIP billing data, this vulnerability must be addressed with high urgency. Administrators should move away from version 4.0.1 immediately and conduct a thorough audit of their system configurations for any signs of past tampering.