---METADATA---
VENDOR: PostgreSQL
PRODUCT: PostgreSQL
AFFECTED_VERSIONS: 18 up to 18.5, 17 up to 17.11, 16 up to 16.15, 15 up to 15.19, 0 up to 14.24
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A SQL injection vulnerability in the PostgreSQL EXTRACT function allows an object owner to execute arbitrary SQL commands as a superuser.

Executive Summary:
A critical SQL injection vulnerability in PostgreSQL allows privilege escalation by object owners, potentially granting them superuser control over the entire database instance.

Vulnerability Details

CVE-ID: CVE-2026-15741

Affected Software: PostgreSQL

Affected Versions: 18 (pre-18.5), 17 (pre-17.11), 16 (pre-16.15), 15 (pre-15.19), and 14 (pre-14.24)

Vulnerability: This is a classic SQL injection vulnerability (CWE-89) found within the EXTRACT function deparse mechanism. It allows a user who already possesses object ownership to execute malicious SQL, effectively elevating their privileges to superuser status.

Business Impact

The ability to escalate privileges to superuser allows an attacker to bypass all database security controls, potentially resulting in complete data theft, modification, or destruction. With a CVSS score of 8.8, this vulnerability poses a severe threat to the integrity and confidentiality of any application relying on the affected PostgreSQL versions.

Remediation Plan

Immediate Action: Apply the vendor-provided security patches by upgrading to the latest minor version for the respective major release (e.g., 18.5, 17.11, etc.).

Proactive Monitoring: Review database audit logs for anomalous SQL commands, specifically those involving the EXTRACT function or attempts to modify sensitive system objects.

Compensating Controls: Restrict the ability of users to create or define new objects if they do not strictly require such privileges, and enforce the principle of least privilege for all database accounts.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Privilege escalation flaws in foundational database software are high-value targets for attackers.

Analyst Recommendation

Database administrators should treat this update with the highest urgency. Upgrade cycles for database engines should be accelerated to address this privilege escalation risk, ensuring that superuser access remains strictly controlled and monitored.

---METADATA---
VENDOR: WGDashboard
PRODUCT: WGDashboard
AFFECTED_VERSIONS: 0 through 4.3.2
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A critical Remote Code Execution vulnerability in WGDashboard versions 0 through 4.3.2 allows for OS command injection via insufficient input validation in API endpoints.

Executive Summary:
A critical Remote Code Execution vulnerability in WGDashboard allows unauthenticated attackers to execute arbitrary commands as root, posing a severe risk of total system compromise.

Vulnerability Details

CVE-ID: CVE-2026-15733

Affected Software: WGDashboard WGDashboard

Affected Versions: 0 through 4.3.2

Vulnerability: The vulnerability is an OS Command Injection flaw (CWE-78) occurring within API endpoints, such as /api/updatePeerSettings. Despite the initial description suggesting authentication requirements, the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is an unauthenticated vulnerability accessible over the network.

Business Impact

Successful exploitation allows an attacker to gain full root-level control over the host running WGDashboard. Given the 9.8 CVSS score, this represents a critical risk that could lead to complete data exfiltration, persistent unauthorized access, and full system takeover. The potential for immediate and total compromise makes this an urgent priority for any organization utilizing this software.

Remediation Plan

Immediate Action: Update WGDashboard to the latest available version that addresses these command injection flaws. If an update is not yet available, restrict access to the WGDashboard administrative interface to trusted internal networks only.

Proactive Monitoring: Review web server access logs for suspicious requests targeting the /api/updatePeerSettings endpoint. Monitor for unusual processes or child processes spawned by the WGDashboard service that may indicate command injection attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block malicious payloads containing shell metacharacters or unauthorized system commands within API request parameters.

Exploitation Status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the provided references and confirmed by the presence of Nuclei detection templates.

Analyst Notes: As of August 6, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The availability of public proof-of-concept code significantly lowers the barrier to entry for potential attackers.

Analyst Recommendation

This is a critical vulnerability that requires immediate attention due to the ease of exploitation and the high level of access granted to attackers. Security teams should prioritize patching or implementing network-level access controls immediately to prevent unauthorized root-level command execution.

---METADATA---
VENDOR: WGDashboard
PRODUCT: WGDashboard
AFFECTED_VERSIONS: 0 through 4.3.2
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A Server-Side Request Forgery (SSRF) vulnerability in WGDashboard allows authenticated attackers to perform arbitrary HTTP requests and retrieve responses via the webhook functionality.

Executive Summary:
A critical SSRF vulnerability in WGDashboard enables authenticated attackers to abuse webhook functionality to make unauthorized internal network requests.

Vulnerability Details

CVE-ID: CVE-2026-15732

Affected Software: WGDashboard WGDashboard

Affected Versions: 0 through 4.3.2

Vulnerability: This is a Server-Side Request Forgery (CWE-918) vulnerability. Although the description specifies authenticated attackers, the CVSS vector indicates network-level access, allowing an attacker to leverage the webhook feature to interact with internal services that are otherwise inaccessible from the external network.

Business Impact

The CVSS score of 9.8 reflects the high potential for internal network reconnaissance and potential lateral movement. By retrieving responses from internal services, an attacker could bypass network perimeters, leading to the compromise of sensitive internal data or administrative interfaces.

Remediation Plan

Immediate Action: Review the vendor advisory for patch availability. If no patch is available for your version, restrict access to the webhook functionality and the WGDashboard administrative interface to trusted internal networks only.

Proactive Monitoring: Inspect outbound traffic from the WGDashboard server for anomalies, specifically targeting requests to internal IP ranges or sensitive internal services.

Compensating Controls: Configure the WGDashboard server with strict egress filtering to prevent it from initiating connections to non-essential internal or external destinations.

Exploitation Status

Public Exploit Available: Yes, a public proof-of-concept is available via GitHub.

Analyst Notes: As of Aug 7, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The existence of public proof-of-concept code significantly lowers the barrier for exploitation.

Analyst Recommendation

Due to the critical severity and the existence of public proof-of-concept code, this vulnerability should be treated as a high-priority risk. Administrators must restrict access to the WGDashboard interface and monitor for any signs of internal network probing until a vendor-supplied patch is installed.

---METADATA---
VENDOR: Red Hat
PRODUCT: Directory Server
AFFECTED_VERSIONS: Red Hat Directory Server 11, 12, 13; Red Hat Enterprise Linux 6, 7, 10
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in the 389 Directory Server (389-ds-base) component, which may allow for a denial of service.

Executive Summary:
A high-severity stack-based buffer overflow flaw in Red Hat Directory Server could lead to a service disruption, as it is exploitable by an unauthenticated remote attacker.

Vulnerability Details

CVE-ID: CVE-2026-15722

Affected Software: Red Hat Directory Server

Affected Versions: Red Hat Directory Server 11, 12, 13; Red Hat Enterprise Linux 6, 7, 10

Vulnerability: This is a stack-based buffer overflow (CWE-121) occurring within the 389 Directory Server codebase. The vulnerability is network-accessible and requires no authentication from the attacker to trigger the buffer corruption.

Business Impact

Successful exploitation of this flaw can result in a denial of service, rendering directory services unavailable to the organization. Given the critical role of directory services in identity management and authentication, such an outage poses a significant risk to operational continuity. With a CVSS score of 7.5, the vulnerability is classified as high severity, primarily due to the ease of remote exploitation.

Remediation Plan

Immediate Action: Consult the official Red Hat security advisory at the provided references to identify and apply the necessary patches or security errata for your specific deployment.

Proactive Monitoring: Monitor server logs for unexpected process crashes, segmentation faults, or irregular traffic patterns targeting directory server ports.

Compensating Controls: Ensure that directory server instances are protected by network-level access controls, such as firewalls, to restrict access to trusted internal segments only.

Exploitation Status

Public Exploit Available: No (unknown).

Analyst Notes: As of August 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its potential for unauthenticated remote impact on a foundational infrastructure component.

Analyst Recommendation

Organizations running Red Hat Directory Server should prioritize the identification of vulnerable instances within their environment. While active exploitation is not currently reported, the potential for remote service disruption necessitates the prompt application of security updates once provided by the vendor.

---METADATA---
VENDOR: Bilin Software and Informatics Consultancy
PRODUCT: HUMANIST Digital Human Resources
AFFECTED_VERSIONS: 26.0 up to (excluding) 26.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
HUMANIST Digital Human Resources contains a cleartext storage vulnerability that facilitates SQL injection, allowing unauthenticated attackers to compromise sensitive application data.

Executive Summary:
A critical SQL injection vulnerability in HUMANIST Digital Human Resources allows unauthenticated attackers to gain unauthorized access to sensitive information stored in the application.

Vulnerability Details

CVE-ID: CVE-2026-15721

Affected Software: Bilin Software and Informatics Consultancy HUMANIST Digital Human Resources

Affected Versions: 26.0 up to (excluding) 26.1

Vulnerability: The application is susceptible to SQL injection (CWE-312/CWE-89) due to improper handling of cleartext sensitive information. This allows an unauthenticated attacker to manipulate backend database queries, potentially leading to unauthorized data exfiltration or modification.

Business Impact

The CVSS score of 9.8 indicates a critical risk of data loss or manipulation. Given that this is a Human Resources management system, a successful exploit could result in the compromise of highly sensitive employee personal information, leading to significant legal and reputational consequences for the organization.

Remediation Plan

Immediate Action: Contact the vendor for the 26.1 update and apply it immediately upon availability.

Proactive Monitoring: Monitor application database logs for anomalous query patterns, such as unexpected syntax or large volumes of data extraction, which may indicate an ongoing SQL injection attempt.

Compensating Controls: Use a Web Application Firewall with SQL injection protection rules enabled to filter malicious input strings before they reach the application layer.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of Aug 4, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability's inherent exploitability is high, as it does not require authentication to interact with the database interface.

Analyst Recommendation

Immediate attention is required to secure the HUMANIST Digital Human Resources platform. Until the vendor-provided update is applied, ensure that the application is isolated from public-facing internet access and verify that all database connection strings follow the principle of least privilege.

---METADATA---
VENDOR: Eclipse Foundation
PRODUCT: Eclipse BaSyx Go Components
AFFECTED_VERSIONS: 0 up to (excluding) 1.0.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Eclipse BaSyx Go Components contains an authorization bypass vulnerability where inconsistent trailing-slash handling allows attackers to circumvent ABAC security policies.

Executive Summary:
An authorization bypass in Eclipse BaSyx Go Components allows unauthenticated attackers to perform unauthorized operations by manipulating request paths.

Vulnerability Details

CVE-ID: CVE-2026-15704

Affected Software: Eclipse Foundation Eclipse BaSyx Go Components

Affected Versions: 0 up to (excluding) 1.0.1

Vulnerability: The software exhibits inconsistent path handling between the HTTP router and ABAC middleware (CWE-863, CWE-284). By appending a trailing slash to a request, an attacker can bypass ABAC authorization checks, allowing for unauthorized read, write, or delete operations on protected API routes.

Business Impact

This flaw undermines the core security model of the affected services, potentially exposing sensitive repository data to unauthorized modification or exfiltration. With a CVSS score of 9.8, this vulnerability poses a critical threat to data integrity and system security, as it effectively neutralizes established access control policies.

Remediation Plan

Immediate Action: Upgrade all deployments of Eclipse BaSyx Go Components to version 1.0.1.

Proactive Monitoring: Review API access logs for anomalous requests featuring trailing slashes or attempts to access restricted endpoints that should be blocked by ABAC.

Compensating Controls: Implement a Web Application Firewall (WAF) to normalize incoming request paths and block requests that attempt to bypass routing security via malformed URL structures.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of Jul 24, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherent to the middleware integration, making it a high-priority architectural fix.

Analyst Recommendation

Given the ease of exploitation and the potential for unauthorized data access, organizations should apply the update to version 1.0.1 without delay. Failure to patch allows attackers to bypass security controls entirely without requiring any authentication.

---METADATA---
VENDOR: Totolink
PRODUCT: NR1800X
AFFECTED_VERSIONS: 9.1.0u.6279_B20210910
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Totolink NR1800X router contains a stack-based buffer overflow vulnerability in the lighttpd component, allowing for remote code execution.

Executive Summary:
A stack-based buffer overflow vulnerability in the Totolink NR1800X router allows remote, unauthenticated attackers to cause memory corruption and potentially execute arbitrary code.

Vulnerability Details

CVE-ID: CVE-2026-15701

Affected Software: Totolink NR1800X

Affected Versions: 9.1.0u.6279_B20210910

Vulnerability: This vulnerability affects the Form_Logout function within the lighttpd component. By manipulating the Host argument, an attacker can trigger a stack-based buffer overflow, which is a form of memory corruption that may lead to remote code execution.

Business Impact

This vulnerability impacts network infrastructure, potentially allowing attackers to gain control over the router, intercept traffic, or pivot into the internal network. With a high CVSS score, this represents a severe risk to network security and perimeter integrity.

Remediation Plan

Immediate Action: Check the official Totolink support website for firmware updates addressing this vulnerability, and apply them as soon as they become available.

Proactive Monitoring: Monitor network traffic for unusual patterns or attempts to communicate with administrative interfaces on the router from external sources.

Compensating Controls: Disable remote management of the router from the WAN interface and ensure the device is segmented from sensitive internal resources where possible.

Exploitation Status

Public Exploit Available: Yes, a public exploit is available via the GitHub repository linked in the referenced vulnerability database.

Analyst Notes: As of July 14, 2026, there is no confirmed active exploitation in the wild; however, a public exploit is available, so exploitation risk should be treated as credible. The presence of a public exploit significantly lowers the barrier to entry for attackers.

Analyst Recommendation

The availability of a public exploit makes this vulnerability highly dangerous. Users should immediately restrict external access to the device and prioritize applying firmware updates to mitigate the risk of remote compromise.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in Tenda BE12 Pro firmware version 16.03.66.23, which could allow an authenticated attacker to trigger memory corruption.

Executive Summary:
A memory corruption vulnerability in the Tenda BE12 Pro router presents a high risk of system compromise for authenticated users.

Vulnerability Details

CVE-ID: CVE-2026-15696

Affected Software: Tenda BE12 Pro

Affected Versions: 16.03.66.23

Vulnerability: This is a stack-based buffer overflow (CWE-121) resulting in memory corruption (CWE-119). The vulnerability is reachable by an attacker with low privileges (PR:L) over the network.

Business Impact

Successful exploitation of this memory corruption flaw can lead to a complete compromise of the router, causing service disruption or potential unauthorized access to network traffic. With a CVSS score of 8.8, this vulnerability is classified as high severity, reflecting the potential for total loss of confidentiality, integrity, and availability of the affected device.

Remediation Plan

Immediate Action: Check the Tenda official support portal for firmware updates addressing this vulnerability and apply them immediately.

Proactive Monitoring: Monitor system logs for unauthorized configuration changes or unexpected device reboots, which may indicate exploitation attempts.

Compensating Controls: Restrict management interface access to trusted internal IP addresses and disable remote management features to reduce the attack surface.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 15, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The nature of stack-based buffer overflows makes this device inherently susceptible to remote code execution if the input is not properly sanitized.

Analyst Recommendation

Given the high CVSS score and the existence of a proof-of-concept, users must prioritize securing their Tenda BE12 Pro devices. Apply the latest firmware updates as soon as they become available and ensure that administrative access to the device is restricted to authorized personnel only.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in the Tenda BE12 Pro router, which may allow an authenticated attacker to trigger memory corruption.

Executive Summary:
A memory corruption vulnerability in the Tenda BE12 Pro router allows authenticated attackers to potentially execute arbitrary code or cause a denial of service.

Vulnerability Details

CVE-ID: CVE-2026-15695

Affected Software: Tenda BE12 Pro

Affected Versions: 16.03.66.23

Vulnerability: The flaw is identified as a stack-based buffer overflow and general memory corruption. According to the CVSS vector, this attack requires the attacker to have low-level privileges (authenticated), meaning the impact is localized to users who have already gained access to the management interface.

Business Impact

With a CVSS score of 8.8, this vulnerability represents a high risk to network infrastructure. If exploited, an attacker could compromise the router's operating system, leading to full network traffic interception, unauthorized configuration changes, or a complete loss of service for the network relying on this hardware.

Remediation Plan

Immediate Action: Check the Tenda support website or the provided VulDB advisory for firmware updates and apply them to all affected BE12 Pro devices.

Proactive Monitoring: Review router management logs for suspicious login activity or unusual administrative commands that could indicate an attempt to trigger the overflow.

Compensating Controls: Restrict access to the router's management interface to a dedicated, isolated management VLAN and disable remote management features to prevent unauthorized access.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability requires authenticated access, which inherently reduces the risk compared to unauthenticated remote flaws.

Analyst Recommendation

Although the vulnerability requires authentication, the potential for total system compromise necessitates prompt attention. Administrators should verify the current firmware version and coordinate a maintenance window to apply the necessary security updates to maintain the integrity of the network perimeter.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in Tenda BE12 Pro firmware version 16.03.66.23, which could allow an authenticated attacker to trigger memory corruption.

Executive Summary:
A critical memory corruption vulnerability in the Tenda BE12 Pro router poses a significant risk of system instability or unauthorized control for authenticated users.

Vulnerability Details

CVE-ID: CVE-2026-15694

Affected Software: Tenda BE12 Pro

Affected Versions: 16.03.66.23

Vulnerability: This flaw is identified as a stack-based buffer overflow (CWE-121) leading to memory corruption (CWE-119). It requires an authenticated user with low privileges to trigger the vulnerable function.

Business Impact

The potential for memory corruption on network infrastructure devices creates a high risk of service denial and potential remote code execution. The CVSS score of 8.8 highlights the critical nature of this flaw, as it allows an authenticated attacker to impact the fundamental integrity and availability of the networking hardware.

Remediation Plan

Immediate Action: Regularly monitor the vendor support page for patch releases and apply the update to version 16.03.66.23 or newer as soon as it is provided.

Proactive Monitoring: Audit network logs for anomalous traffic patterns or unexpected administrative actions originating from low-privilege accounts.

Compensating Controls: Implement network segmentation to isolate the management interface of the router from general user traffic.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 15, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. Buffer overflow vulnerabilities in embedded firmware typically allow for severe impacts on device stability.

Analyst Recommendation

The severity of this issue necessitates immediate attention from network administrators. Until a patch is deployed, restrict access to the device management interface to minimize the risk posed by potential attackers who have obtained low-level user credentials.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in Tenda BE12 Pro firmware version 16.03.66.23, which could allow an authenticated attacker to trigger memory corruption.

Executive Summary:
A memory corruption vulnerability in the Tenda BE12 Pro router presents a high risk of system compromise for authenticated users.

Vulnerability Details

CVE-ID: CVE-2026-15693

Affected Software: Tenda BE12 Pro

Affected Versions: 16.03.66.23

Vulnerability: This vulnerability involves a stack-based buffer overflow (CWE-121) and subsequent memory corruption (CWE-119). It is exploitable by an authenticated user with low privileges.

Business Impact

Exploitation of this memory corruption vulnerability could result in unauthorized administrative control or severe service disruption. The CVSS score of 8.8 reflects the high danger associated with such flaws in networking equipment, as they can lead to the loss of control over critical infrastructure components.

Remediation Plan

Immediate Action: Check the Tenda website for official firmware updates and apply the latest security patches once released.

Proactive Monitoring: Review security logs for indicators of memory corruption, such as recurring process crashes or unexpected service restarts.

Compensating Controls: Configure access control lists to limit administrative access to the router to trusted, secure internal workstations.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 15, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. Memory corruption flaws are often leveraged to gain unauthorized code execution on embedded systems.

Analyst Recommendation

Due to the high severity and the presence of a proof-of-concept, it is imperative to mitigate this risk. Ensure that all firmware is kept up to date and that account security policies are strictly enforced to prevent low-privilege users from gaining the access required to trigger this vulnerability.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: Tenda BE12 Pro: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A memory corruption vulnerability exists in the Tenda BE12 Pro router, specifically involving a stack-based buffer overflow.

Executive Summary:
A high-severity buffer overflow vulnerability in the Tenda BE12 Pro router poses a risk of system instability and unauthorized command execution.

Vulnerability Details

CVE-ID: CVE-2026-15692

Affected Software: Tenda BE12 Pro

Affected Versions: Tenda BE12 Pro: 16.03.66.23

Vulnerability: This is a stack-based buffer overflow (CWE-121) and memory corruption (CWE-119) vulnerability. Exploitation requires the attacker to hold low-level authenticated access to the target system.

Business Impact

The CVSS score of 8.8 reflects the high potential for total system compromise if the memory corruption is leveraged for code execution. This poses a severe risk to business operations, as a compromised router can be used as a pivot point for further attacks on the internal network.

Remediation Plan

Immediate Action: Keep the device firmware updated and apply the vendor patch immediately upon its release to address the memory corruption flaw.

Proactive Monitoring: Audit system logs for signs of unexpected reboots or crashes, which can be indicators of failed or successful buffer overflow attempts.

Compensating Controls: Implement strict network segmentation and ensure that the router management interface is not exposed to untrusted networks.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 15, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The presence of a proof-of-concept necessitates proactive defense measures even in the absence of a vendor patch.

Analyst Recommendation

Given the availability of a proof-of-concept, this vulnerability is considered a credible threat. Administrators must prioritize limiting the attack surface by restricting access to the device and monitoring for vendor-supplied firmware updates to resolve the underlying memory management issues.

---METADATA---
VENDOR: Tenda
PRODUCT: BE12 Pro
AFFECTED_VERSIONS: Tenda BE12 Pro: 16.03.66.23
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability in the Tenda BE12 Pro router allows for potential memory corruption.

Executive Summary:
A critical memory corruption vulnerability in the Tenda BE12 Pro router allows authenticated attackers to potentially execute arbitrary code.

Vulnerability Details

CVE-ID: CVE-2026-15691

Affected Software: Tenda BE12 Pro

Affected Versions: Tenda BE12 Pro: 16.03.66.23

Vulnerability: This vulnerability is caused by a stack-based buffer overflow, classified as CWE-121 and CWE-119. It requires the attacker to have low-level privileges (authenticated access) to trigger the memory corruption.

Business Impact

The successful exploitation of this vulnerability could lead to a complete compromise of the router's functionality, potentially resulting in unauthorized access to the network or a total denial of service. Given the high CVSS score of 8.8, this flaw represents a significant risk to operational continuity and network security, particularly if the device serves as a primary gateway.

Remediation Plan

Immediate Action: Monitor the official Tenda support portal for firmware releases and apply the security update as soon as a patch is issued.

Proactive Monitoring: Review device access logs for unusual administrative activity or repeated connection attempts that may indicate exploitation efforts.

Compensating Controls: Restrict administrative access to the router interface to trusted internal IP addresses only, and ensure the device is not reachable from the public internet.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its potential for remote code execution via memory corruption, but it currently lacks verified public exploit code.

Analyst Recommendation

Organizations utilizing the Tenda BE12 Pro should treat this vulnerability with high priority. While a specific patch version is currently pending, administrators must implement network-level access controls immediately to mitigate the risk of exploitation by authenticated users.

---METADATA---
VENDOR: Ollama
PRODUCT: Ollama
AFFECTED_VERSIONS: 0.7.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Ollama is affected by a denial-of-service vulnerability due to improper validation of array indices in the downloadBlob function.

Executive Summary:
A denial-of-service vulnerability in Ollama version 0.7.1 allows remote attackers to crash the service by exploiting improper array index validation.

Vulnerability Details

CVE-ID: CVE-2026-15685

Affected Software: Ollama Ollama

Affected Versions: 0.7.1

Vulnerability: This flaw (CWE-129) occurs within the downloadBlob function, where improper validation of array indices allows an unauthenticated remote attacker to trigger a crash, leading to a denial-of-service condition.

Business Impact

The CVSS score of 7.5 reflects the high impact on service availability. An attacker can remotely disrupt the operation of the Ollama service, resulting in downtime for any applications or workflows dependent on the model-running platform.

Remediation Plan

Immediate Action: Monitor official Ollama release channels for a patch and update to the latest available version as soon as it is released.

Proactive Monitoring: Monitor service uptime and logs for crash events or unexpected process terminations that may indicate exploitation attempts.

Compensating Controls: Limit access to the Ollama API interface via a firewall or reverse proxy to only allow trusted clients, thereby reducing the risk of exploitation by unauthorized remote actors.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently simple to trigger, increasing the risk of automated scanning and exploitation.

Analyst Recommendation

Given the potential for service disruption, users should restrict network access to the Ollama service interface as a temporary measure. Once a fix is provided by the vendor, it should be deployed as a matter of priority to restore the availability and stability of the platform.

---METADATA---
VENDOR: Lorex
PRODUCT: 2K Indoor Wi-Fi Security Camera
AFFECTED_VERSIONS: 2.800.020000000.3.R.20220331
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Lorex 2K Indoor Wi-Fi Security Camera device management server fails to properly validate certificates, potentially allowing man-in-the-middle attacks.

Executive Summary:
A certificate validation vulnerability in the Lorex 2K Indoor Wi-Fi Security Camera management server exposes users to potential interception and compromise of sensitive traffic.

Vulnerability Details

CVE-ID: CVE-2026-15683

Affected Software: Lorex 2K Indoor Wi-Fi Security Camera

Affected Versions: 2.800.020000000.3.R.20220331

Vulnerability: This vulnerability (CWE-295) allows an attacker on the adjacent network (AV:A) to perform man-in-the-middle attacks by exploiting the improper validation of SSL/TLS certificates during management communications.

Business Impact

With a CVSS score of 7.5, this vulnerability represents a significant risk to the privacy and integrity of camera data. An attacker could intercept video streams or manipulate management commands, leading to total loss of device control and potential physical security compromise.

Remediation Plan

Immediate Action: Check the Lorex support portal for firmware updates; if no update is available, isolate the device from the public internet and restrict access to authorized management segments only.

Proactive Monitoring: Monitor for anomalous traffic patterns or unauthorized connections originating from the management port of the camera.

Compensating Controls: Utilize a dedicated VLAN for IoT devices to minimize the impact of an adjacent network attack and ensure that management interfaces are not accessible from untrusted segments.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for the attacker to be on the adjacent network limits the potential threat surface to local network compromises.

Analyst Recommendation

The vulnerability is severe due to the potential for total device compromise. Administrators should verify the status of their firmware and apply any vendor-supplied patches immediately upon release to ensure secure communication channels.

---METADATA---
VENDOR: Lorex
PRODUCT: 2K Indoor Wi-Fi Security Camera
AFFECTED_VERSIONS: 2.800.020000000.3.R.20220331
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Lorex 2K Indoor Wi-Fi Security Camera is vulnerable to a format string flaw in CDeviceOperator, which could allow an unauthenticated attacker to execute arbitrary code remotely.

Executive Summary:
A remote code execution vulnerability in the Lorex 2K Indoor Wi-Fi Security Camera poses a critical risk to device integrity and network security.

Vulnerability Details

CVE-ID: CVE-2026-15680

Affected Software: Lorex 2K Indoor Wi-Fi Security Camera

Affected Versions: 2.800.020000000.3.R.20220331

Vulnerability: The device suffers from a CWE-134 Format String vulnerability within the CDeviceOperator component. This flaw allows an unauthenticated attacker to inject malicious format specifiers to corrupt memory and execute arbitrary code on the affected camera.

Business Impact

Successful exploitation of this vulnerability could lead to a full system compromise, allowing attackers to gain unauthorized access to camera feeds, exfiltrate sensitive data, or pivot into the internal network. With a CVSS score of 7.5, this high-severity vulnerability represents a significant risk to operational security and user privacy, especially for devices deployed in sensitive environments.

Remediation Plan

Immediate Action: Contact the vendor immediately to obtain firmware updates that address this format string vulnerability. If no patch is currently available, isolate the device from public internet access.

Proactive Monitoring: Review network traffic logs for anomalous inbound requests directed toward the camera’s management interface.

Compensating Controls: Implement strict network segmentation and place the camera behind a firewall that restricts access to only trusted management IP addresses.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the potential for remote code execution without user interaction.

Analyst Recommendation

Given the high CVSS score and the nature of the vulnerability, organizations should prioritize the security of these cameras. If firmware updates are unavailable, the most effective mitigation is to disconnect the device from the internet until a vendor-supplied patch is applied.

---METADATA---
VENDOR: Rapid7
PRODUCT: InsightVM
AFFECTED_VERSIONS: Versions before 8.34.0
---END_METADATA---

Description Summary:
Rapid7 InsightVM versions before 8.34.0 contain a signature verification flaw in the ACS endpoint. This allows unauthenticated attackers to bypass authentication and achieve full account takeover.

Executive Summary:
A critical authentication bypass vulnerability in Rapid7 InsightVM allows unauthenticated attackers to hijack Security Console accounts and gain full administrative control over the environment.

Vulnerability Details

CVE-ID: CVE-2026-1568

Affected Software: Rapid7 InsightVM

Affected Versions: Versions prior to 8.34.0

Vulnerability: This vulnerability stems from a failure to verify signatures on the Assertion Consumer Service (ACS) cloud endpoint. An unauthenticated remote attacker can submit unsigned assertions to the endpoint, which the application processes to issue valid session cookies for targeted user accounts.

Business Impact

The potential consequences of this flaw are severe, as it enables a complete compromise of the InsightVM Security Console. Successful exploitation allows an attacker to gain full account takeover, providing access to sensitive vulnerability data, asset configurations, and security reporting. With a CVSS score of 9.6, this represents a Critical risk to organizational data integrity and confidentiality.

Remediation Plan

Immediate Action: Administrators must upgrade Rapid7 InsightVM to version 8.34.0 or later immediately to patch the signature verification logic.

Proactive Monitoring: Security teams should review access logs for the ACS endpoint for any anomalous session generation or unrecognized login events originating from external IP addresses.

Compensating Controls: Ensure the Security Console is not exposed to the public internet and restrict access to the web interface via a VPN or trusted management network.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Feb 3, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the critical nature of the flaw and the ease of bypassing authentication, the potential for exploitation is extremely high.

Analyst Recommendation

This vulnerability represents a significant threat to the security posture of any organization utilizing Rapid7 InsightVM. The ability for an unauthenticated attacker to bypass authentication mechanisms and take over administrative accounts is a worst-case scenario. It is strongly recommended that the patch to version 8.34.0 be applied within 24 hours to mitigate the risk of exploitation.

---METADATA---
VENDOR: Fastify
PRODUCT: @fastify/http-proxy
AFFECTED_VERSIONS: 9.4.0 up to (excluding) 11.6.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A path traversal vulnerability in @fastify/http-proxy allows unauthenticated remote attackers to access restricted directory structures on the host system.

Executive Summary:
A path traversal vulnerability in the @fastify/http-proxy package poses a high risk of unauthorized file system access due to improper input validation.

Vulnerability Details

CVE-ID: CVE-2026-15631

Affected Software: Fastify @fastify/http-proxy

Affected Versions: 9.4.0 up to (excluding) 11.6.0

Vulnerability: This is a path traversal vulnerability (CWE-22) occurring within the proxy module. It allows an unauthenticated attacker to manipulate file paths and potentially access sensitive data outside of the intended directory.

Business Impact

Successful exploitation allows unauthorized access to sensitive files on the underlying server, which could lead to full system compromise or the exposure of proprietary configuration data. With a CVSS score of 8.7, this vulnerability is classified as high severity, reflecting the potential for significant impact on confidentiality and integrity.

Remediation Plan

Immediate Action: Update the @fastify/http-proxy package to version 11.6.0 or later to include the necessary path validation logic.

Proactive Monitoring: Review application access logs for suspicious URL patterns containing directory traversal sequences, such as dot-dot-slash (../) strings, targeting the proxy endpoint.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block incoming requests containing directory traversal characters directed at the proxy service.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 19, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's inherent exploitability remains a concern for any environment exposing the proxy to untrusted networks.

Analyst Recommendation

Given the critical nature of path traversal vulnerabilities in proxy components, immediate patching is required. Organizations should prioritize updating to version 11.6.0 to eliminate the vulnerability and prevent potential unauthorized access to the host file system.

---METADATA---
VENDOR: Google Cloud
PRODUCT: Google SecOps (Chronicle SOAR)
AFFECTED_VERSIONS: 0 up to (excluding) 6.3.85
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A SQL injection vulnerability in a legacy dashboard widget API of Google SecOps (Chronicle SOAR) allows authenticated attackers to execute unauthorized blind SQL queries.

Executive Summary:
A critical SQL injection vulnerability in Google SecOps (Chronicle SOAR) allows authenticated attackers to manipulate database queries via a legacy dashboard widget API.

Vulnerability Details

CVE-ID: CVE-2026-15623

Affected Software: Google Cloud Google SecOps (Chronicle SOAR)

Affected Versions: 0 up to (excluding) 6.3.85

Vulnerability: The vulnerability exists within a legacy dashboard widget API that fails to properly neutralize input in a request parameter. An authenticated attacker can leverage this flaw to execute blind SQL queries against the underlying database.

Business Impact

Successful exploitation could lead to unauthorized access to sensitive security data and potential compromise of the SOAR platform configuration. With a CVSS score of 9.4, the risk is critical as it impacts the integrity and confidentiality of security operations data.

Remediation Plan

Immediate Action: Verify that the system is running version 6.3.85 or later, as the vendor has confirmed the patch is already applied in this release.

Proactive Monitoring: Review audit logs for suspicious API calls directed at dashboard widgets to identify potential unauthorized activity.

Compensating Controls: Ensure that access to the Google SecOps platform is restricted to authorized personnel using strong multi-factor authentication to limit the pool of potential attackers.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of Aug 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw requires an authenticated session, which slightly mitigates the attack surface compared to unauthenticated vulnerabilities.

Analyst Recommendation

While the vendor has already released a patch, organizations should confirm their version status immediately. Ensuring all instances are on version 6.3.85 or later is the definitive step to eliminate this risk.

---METADATA---
VENDOR: Logto
PRODUCT: Logto
AFFECTED_VERSIONS: Logto Logto: 1.21.0 through 1.37.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Logto fails to invalidate IdP-initiated SAML sessions after use, enabling session replay attacks within the session validity window.

Executive Summary:
A critical authentication bypass vulnerability in Logto allows for the replay of SAML sessions, potentially enabling unauthorized account access.

Vulnerability Details

CVE-ID: CVE-2026-15614

Affected Software: Logto

Affected Versions: Logto Logto: 1.21.0 through 1.37.1

Vulnerability: The application fails to properly delete IdP-initiated SAML sessions, resulting in an authentication bypass by capture-replay. This is an unauthenticated vulnerability that can be exploited by intercepting valid session data.

Business Impact

This vulnerability carries a CVSS score of 7.5, reflecting its potential to grant attackers unauthorized access to user accounts. Such access could lead to significant data breaches, privilege escalation, and total compromise of user-related information within the Logto ecosystem.

Remediation Plan

Immediate Action: Update the Logto installation to the latest version to ensure that SAML session invalidation is properly implemented.

Proactive Monitoring: Review authentication logs for anomalous session patterns or repeated SAML assertions that may indicate replay attempts.

Compensating Controls: Implement strict session timeout policies and utilize network-level monitoring to detect suspicious SAML traffic.

Exploitation Status

Public Exploit Available: No (unknown)

Analyst Notes: As of July 23, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently dangerous because it allows attackers to bypass standard authentication flows using captured session tokens.

Analyst Recommendation

Given the potential for unauthorized account access, this update should be treated as a high priority. Organizations should upgrade to a patched version immediately to close the session replay window.

---METADATA---
VENDOR: WordPress
PRODUCT: Frontend Admin by DynamiApps
AFFECTED_VERSIONS: 0 through 3.29.9
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Frontend Admin by DynamiApps plugin for WordPress contains an authorization bypass vulnerability, allowing authenticated users to perform unauthorized actions due to missing capability checks.

Executive Summary:
An authorization bypass vulnerability in the Frontend Admin by DynamiApps WordPress plugin allows authenticated users to escalate privileges, posing a severe threat to site security.

Vulnerability Details

CVE-ID: CVE-2026-15606

Affected Software: WordPress Frontend Admin by DynamiApps (acf-frontend-form-element)

Affected Versions: 0 through 3.29.9

Vulnerability: This is a missing authorization vulnerability (CWE-862) where the plugin fails to perform adequate capability checks on administrative functions. This allows an authenticated user to perform actions they are not permitted to execute.

Business Impact

With a CVSS score of 8.8, this vulnerability allows for full unauthorized access and modification of site data. An attacker could potentially take control of administrative functions, leading to total compromise of the WordPress installation and its associated content.

Remediation Plan

Immediate Action: Update the Frontend Admin by DynamiApps plugin to version 3.29.10 or later immediately.

Proactive Monitoring: Review user activity logs for unauthorized administrative actions or modifications to sensitive site settings during the period the plugin was outdated.

Compensating Controls: If an immediate update is not feasible, deactivate the plugin until the patch can be applied, or use a Web Application Firewall (WAF) to block requests targeting the vulnerable plugin endpoints.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 12, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherent in the plugin's code logic, which lacks necessary permission validation for core functions.

Analyst Recommendation

The vulnerability is critical for WordPress site integrity. Administrators should prioritize updating the Frontend Admin by DynamiApps plugin to version 3.29.10 to eliminate the authorization bypass risk and prevent potential site takeover.

---METADATA---
VENDOR: Red Hat
PRODUCT: OpenShift
AFFECTED_VERSIONS: Red Hat Pen Drive Powered by Red Hat Lightspeed
CONFIDENCE: medium
MISSING: patch, technical_details
---END_METADATA---

Description Summary:
The OpenShift incluster-checks tool contains a privilege escalation flaw allowing authenticated users to gain root access on cluster nodes via privileged debug pods.

Executive Summary:
A high-severity privilege escalation vulnerability in the OpenShift incluster-checks tool allows authenticated users to obtain root access on underlying cluster nodes.

Vulnerability Details

CVE-ID: CVE-2026-15584

Affected Software: Red Hat OpenShift

Affected Versions: Red Hat Pen Drive Powered by Red Hat Lightspeed

Vulnerability: This vulnerability involves execution with unnecessary privileges (CWE-250). The incluster-checks tool creates privileged debug pods that mount the host filesystem in a shared namespace, which allows an authenticated user with the standard edit role to interact with these pods and escalate their privileges to root on the node.

Business Impact

A successful exploit allows an authenticated user to break out of the container environment and gain full root control over the cluster nodes. This level of access grants the attacker total control over the node, including the ability to steal data, deploy persistent backdoors, or disrupt all workloads running on that node. The CVSS score of 7.5 highlights the substantial risk to the entire cluster infrastructure.

Remediation Plan

Immediate Action: Review the vendor advisory for specific patch availability and apply all recommended updates to the OpenShift environment.

Proactive Monitoring: Monitor for the creation of unauthorized debug pods or unexpected container execution within the default namespace.

Compensating Controls: Restrict access to the edit role and implement strict Kubernetes admission controllers to prevent the creation of privileged pods by unauthorized users.

Exploitation Status

Public Exploit Available: No (unknown)

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is dangerous due to the ease with which an authenticated user can leverage standard permissions to gain administrative control.

Analyst Recommendation

This vulnerability represents a significant risk to cluster security. Administrators must treat this as a high-priority issue, restricting permissions for the edit role and monitoring for suspicious activity until a formal patch can be deployed to the incluster-checks tool.

---METADATA---
VENDOR: Grafana
PRODUCT: Grafana MCP Server
AFFECTED_VERSIONS: 0.0.0 through 0.17.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Grafana MCP Server is vulnerable to a confused-deputy attack, allowing unauthenticated remote attackers to exfiltrate service-account tokens via a crafted X-Grafana-URL header.

Executive Summary:
A high-severity confused-deputy flaw in Grafana MCP Server allows unauthenticated attackers to exfiltrate sensitive service-account tokens, risking full compromise of integrated systems.

Vulnerability Details

CVE-ID: CVE-2026-15583

Affected Software: Grafana Grafana MCP Server

Affected Versions: 0.0.0 through 0.17.1

Vulnerability: This is a confused-deputy vulnerability that occurs when the server processes a crafted X-Grafana-URL request header. The vulnerability is remotely exploitable by unauthenticated attackers, leading to the unauthorized disclosure of environment-configured tokens.

Business Impact

The exfiltration of a Grafana service-account token grants the attacker the same permissions as the service account, which may include administrative access to Grafana and connected data sources. With a CVSS score of 8.6, this flaw poses a severe risk of lateral movement and large-scale data compromise within the infrastructure.

Remediation Plan

Immediate Action: Upgrade Grafana MCP Server to the latest patched version provided by the vendor to prevent the processing of malicious URL headers.

Proactive Monitoring: Monitor network traffic and server logs for requests containing suspicious or anomalous X-Grafana-URL headers.

Compensating Controls: Implement network-level egress filtering to restrict the server from communicating with unauthorized or untrusted external URLs.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly concerning because it allows for the theft of high-privilege credentials without requiring prior authentication.

Analyst Recommendation

Given the potential for complete service-account compromise, immediate remediation is required. Security teams should identify all instances of the affected Grafana MCP Server and apply the vendor-provided updates to mitigate this vulnerability.

---METADATA---
VENDOR: Red Hat
PRODUCT: OpenShift AI
AFFECTED_VERSIONS: Red Hat OpenShift AI 3.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A flaw in the TrustyAI Service (TAS) deployment of Red Hat OpenShift AI 3.3 results in missing authentication for critical functions.

Executive Summary:
A critical authentication bypass vulnerability in Red Hat OpenShift AI 3.3 could allow adjacent attackers to compromise the TrustyAI Service.

Vulnerability Details

CVE-ID: CVE-2026-15581

Affected Software: Red Hat OpenShift AI

Affected Versions: Red Hat OpenShift AI 3.3

Vulnerability: This vulnerability is caused by missing authentication for critical functions (CWE-306) in the TrustyAI Service. The CVSS vector (AV:A/PR:L) indicates that an authenticated user on the adjacent network can impact the confidentiality, integrity, and availability of the service.

Business Impact

The lack of authentication for sensitive functions exposes the TrustyAI Service to full compromise by authorized users on the same network. Given the CVSS score of 8.0, this vulnerability poses a high risk to the availability and data integrity of AI-driven workflows, which could result in significant operational disruption.

Remediation Plan

Immediate Action: Upgrade to Red Hat OpenShift AI 3.3, specifically utilizing the build/release 1785187521 or later, as detailed in the official Red Hat security advisory RHSA-2026:53263.

Proactive Monitoring: Monitor network traffic and authentication logs for anomalous access attempts targeting the TrustyAI Service endpoints.

Compensating Controls: Ensure that network segmentation is enforced to limit access to the TAS deployment to authorized personnel only, reducing the risk of adjacent network exploitation.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 11, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for adjacent network access moderately constrains the exploitability of this flaw.

Analyst Recommendation

Given the potential for total service compromise, it is imperative that organizations apply the provided updates immediately. Verify that all instances of the TrustyAI Service are patched to the required version to eliminate this authentication gap.

---METADATA---
VENDOR: Red Hat
PRODUCT: OpenShift AI (RHOAI)
AFFECTED_VERSIONS: Red Hat OpenShift AI (RHOAI) component rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9. All previous versions of packages in any minor update stream are assumed vulnerable.
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A flaw in the vllm-orchestrator-gateway component of Red Hat OpenShift AI causes sensitive information exposure by logging bearer tokens and chat payloads at DEBUG level.

Executive Summary:
A hard-coded DEBUG logging configuration in Red Hat OpenShift AI leads to the exposure of sensitive authentication headers and conversation data to unauthorized users with log access.

Vulnerability Details

CVE-ID: CVE-2026-15574

Affected Software: Red Hat OpenShift AI (RHOAI)

Affected Versions: Red Hat OpenShift AI (RHOAI) component rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9. All previous versions of packages in any minor update stream are assumed vulnerable.

Vulnerability: This is an insertion of sensitive information into an externally accessible file or directory (CWE-538). The gateway component logs full authorization headers and chat payloads before filtering occurs, allowing any user with access to cluster logs to intercept sensitive information.

Business Impact

The vulnerability carries a CVSS base score of 7.5, indicating a high risk of sensitive data compromise. Because the logs capture bearer tokens, attackers who gain read access to cluster logs can perform account impersonation or access protected AI model resources, leading to potential data breaches and unauthorized manipulation of AI services.

Remediation Plan

Immediate Action: Configure the RUST_LOG environment variable for the vllm-orchestrator-gateway component to a level higher than DEBUG, such as INFO, to prevent sensitive data from being written to logs.

Proactive Monitoring: Audit existing cluster logs for any instances of authorization headers or chat payloads that may have been captured while the system was in the vulnerable configuration.

Compensating Controls: Restrict access to cluster logs and observability tools to the minimum necessary personnel to reduce the exposure window while the logging configuration is being remediated.

Exploitation Status

Public Exploit Available: No (false)

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability is easily triggered, it requires an attacker to already possess the capability to read cluster-level logs.

Analyst Recommendation

Given the ease of potential credential theft, administrators should prioritize updating the RUST_LOG environment variable immediately. Ensure that logging policies are reviewed to prevent the accidental exposure of sensitive payloads in future deployment cycles.

---METADATA---
VENDOR: Red Hat
PRODUCT: Red Hat build of Keycloak
AFFECTED_VERSIONS: 26.4.0 through 26.4.13, 26.6.0 through 26.6.4
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A type confusion flaw in the Dynamic Client Registration security policy management of the Red Hat build of Keycloak allows authenticated users to impact system security.

Executive Summary:
A type confusion vulnerability in Keycloak allows authenticated attackers to potentially bypass security policies and compromise system integrity.

Vulnerability Details

CVE-ID: CVE-2026-15572

Affected Software: Red Hat build of Keycloak

Affected Versions: 26.4.0 through 26.4.13, 26.6.0 through 26.6.4

Vulnerability: This is a type confusion vulnerability (CWE-843) within the Dynamic Client Registration (DCR) policy management. It requires the attacker to have low-level privileges to successfully trigger the flaw and manipulate resource access.

Business Impact

With a CVSS score of 8.8, this flaw poses a significant risk to identity management infrastructure. An attacker with minimal privileges could escalate their impact by manipulating client registration policies, potentially leading to unauthorized access to applications relying on Keycloak for authentication.

Remediation Plan

Immediate Action: Update the Red Hat build of Keycloak to the fixed versions (26.4.14-1, 26.4-22, 26.6.5-1, or 26.6-11) as detailed in the Red Hat errata.

Proactive Monitoring: Audit logs for unusual Dynamic Client Registration activities and review changes to client security policies that were not initiated by authorized administrators.

Compensating Controls: Enforce strict access control policies for DCR and limit the number of users with permissions to modify registration settings.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While this requires authentication, the impact is severe enough to warrant immediate patching in production identity environments.

Analyst Recommendation

Identity providers are high-value targets. Organizations should treat this vulnerability as critical and ensure that all instances of the Red Hat build of Keycloak are updated to the latest secure versions to prevent potential privilege escalation and unauthorized client registration.

---METADATA---
VENDOR: Vestel
PRODUCT: Telefunken TE24553B45V2DZ Smart TV
AFFECTED_VERSIONS: V2.78.0.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A Server-Side Request Forgery (SSRF) vulnerability in the SmartCenter component of the Telefunken TE24553B45V2DZ Smart TV allows local network attackers to trigger unauthorized internal requests.

Executive Summary:
A high-severity SSRF vulnerability in the Vestel Smart TV platform allows local network attackers to force the device browser to access sensitive internal or loopback destinations.

Vulnerability Details

CVE-ID: CVE-2026-15570

Affected Software: Vestel Telefunken TE24553B45V2DZ Smart TV

Affected Versions: V2.78.0.0

Vulnerability: This is a Server-Side Request Forgery (CWE-918) vulnerability in the SmartCenter browserseturl command, which fails to restrict the URL schemes and destinations that the browser can visit when triggered by a local network attacker.

Business Impact

An attacker on the same local network can use this vulnerability to bypass network security perimeters, potentially interacting with internal services that are otherwise inaccessible from the public internet. Given the CVSS score of 7.1, this poses a risk of unauthorized information gathering or interaction with internal administrative interfaces.

Remediation Plan

Immediate Action: Upgrade the TV firmware to version V2.85.2.0 as provided by the manufacturer.

Proactive Monitoring: Monitor local network traffic for suspicious HTTP requests originating from the Smart TV IP address, particularly those targeting internal IP ranges or 127.0.0.1.

Compensating Controls: Isolate the Smart TV on a separate VLAN or guest network to prevent direct access to internal, sensitive network segments and resources.

Exploitation Status

Public Exploit Available: No (exploit_available: false).

Analyst Notes: As of August 9, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The nature of the flaw requires the attacker to have access to the local network.

Analyst Recommendation

Owners of the affected Telefunken Smart TV should apply the provided firmware update immediately. If an update is not immediately feasible, network isolation is strongly recommended to mitigate the risk of local network-based SSRF attacks.

---METADATA---
VENDOR: Red Hat
PRODUCT: JBoss Enterprise Application Platform
AFFECTED_VERSIONS: 7.4 ELS on RHEL 7
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A deserialization vulnerability in Red Hat JBoss Enterprise Application Platform allows unauthorized remote code execution via untrusted data.

Executive Summary:
A critical deserialization flaw in Red Hat JBoss Enterprise Application Platform (7.4 ELS) permits unauthenticated attackers to execute arbitrary code with the privileges of the application process.

Vulnerability Details

CVE-ID: CVE-2026-15555

Affected Software: Red Hat JBoss Enterprise Application Platform

Affected Versions: 7.4 ELS on RHEL 7

Vulnerability: The vulnerability is identified as a deserialization of untrusted data (CWE-502) within the JBoss marshalling component. An attacker can leverage this flaw to achieve remote code execution, as the system fails to properly validate incoming data streams before processing them.

Business Impact

The vulnerability carries a CVSS score of 8.8, reflecting a high risk of total system compromise. Successful exploitation allows an attacker to gain full control over the application server, potentially resulting in unauthorized data access, modification, or complete service disruption. This poses a severe threat to the integrity and availability of business-critical workflows managed by the JBoss platform.

Remediation Plan

Immediate Action: Update the JBoss Enterprise Application Platform components to the versions specified in the vendor advisory (RHSA-2026:53644), specifically ensuring the JBoss marshalling packages are upgraded to the versions provided in the enrichment data.

Proactive Monitoring: Review application and system access logs for suspicious serialized objects or unexpected network traffic patterns originating from unauthorized sources.

Compensating Controls: Implement strict network segmentation and egress filtering to limit the reach of the application server, and utilize a Web Application Firewall (WAF) to inspect traffic for common deserialization attack signatures.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of August 12, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the flaw is theoretically dangerous due to the nature of deserialization attacks, it is not currently flagged as an active threat.

Analyst Recommendation

Given the high impact of remote code execution, administrators must prioritize patching the affected JBoss components immediately. Adherence to the vendor-provided errata (RHSA-2026:53644) is the only definitive method to eliminate this vulnerability from the environment.

---METADATA---
VENDOR: Owen
PRODUCT: WebStack
AFFECTED_VERSIONS: 0 through 1.2024
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The WebStack WordPress theme is vulnerable to unauthenticated arbitrary file uploads via the io_img_upload() function, potentially leading to remote code execution.

Executive Summary:
A critical vulnerability in the WebStack theme for WordPress allows unauthenticated attackers to execute arbitrary code on the host server.

Vulnerability Details

CVE-ID: CVE-2026-1555

Affected Software: Owen WebStack

Affected Versions: 0 through 1.2024

Vulnerability: This is an unrestricted file upload vulnerability (CWE-434) within the io_img_upload() function. The lack of file type validation allows unauthenticated remote attackers to upload malicious scripts directly to the server.

Business Impact

The CVSS score of 9.8 reflects the extreme severity of this flaw, as it allows full system compromise without user interaction or authentication. Successful exploitation grants an attacker the ability to execute remote code, leading to complete data exfiltration, site defacement, or the establishment of a persistent backdoor within the infrastructure.

Remediation Plan

Immediate Action: As no official patch is currently available, administrators must immediately deactivate and remove the WebStack theme from all WordPress installations until a secure version is released.

Proactive Monitoring: Review web server access logs for anomalous POST requests directed at files within the theme's directory structure, particularly those involving file uploads.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block file uploads to the theme's directory and restrict access to executable scripts in upload folders.

Exploitation Status

Public Exploit Available: Yes — a public proof-of-concept repository exists on GitHub.

Analyst Notes: As of April 15, 2026, there is no public information indicating active exploitation in the wild, though a public proof-of-concept exists. The vulnerability is highly exploitable due to the absence of authentication requirements and the direct nature of the file upload flaw.

Analyst Recommendation

Given the critical CVSS severity and the existence of public proof-of-concept code, this vulnerability poses an immediate threat. Organizations must prioritize the removal of the vulnerable theme immediately. If the theme is business-critical, transition to an alternative solution until the vendor provides a verified security update.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Shibby Tomato firmware versions 1.0 through 1.7 are vulnerable to stack-based buffer overflows and memory corruption, which can lead to system crashes or arbitrary code execution.

Executive Summary:
Critical memory corruption vulnerabilities in Shibby Tomato firmware versions 1.0–1.7 allow authenticated attackers to trigger buffer overflows and potentially gain full control of the device.

Vulnerability Details

CVE-ID: CVE-2026-15548

Affected Software: Shibby Tomato

Affected Versions: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7

Vulnerability: This is a combination of Stack-based Buffer Overflow (CWE-121) and Memory Corruption (CWE-119). These flaws allow an authenticated user to send specially crafted packets that corrupt system memory.

Business Impact

Exploitation of these vulnerabilities can lead to a complete denial-of-service (DoS) or remote code execution on the router or network appliance. Given the CVSS score of 8.8, this is a high-severity issue that could grant an attacker persistent access to the network, facilitating lateral movement and data interception.

Remediation Plan

Immediate Action: Check for and apply the latest available firmware updates from the vendor or migrate to a supported, patched version.

Proactive Monitoring: Monitor device traffic for anomalous packet patterns and unexpected reboots, which are common indicators of memory corruption attempts.

Compensating Controls: Restrict administrative access to the device interface to trusted management subnets and disable unnecessary services that may provide an attack surface.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the EPSS score indicates a moderate probability of exploitation, no weaponized exploit is currently confirmed.

Analyst Recommendation

Due to the nature of firmware-level vulnerabilities, the risk of device compromise is significant. Affected users must monitor the vendor's security portal for a patch and apply it immediately upon availability. If no patch is released, consider replacing the hardware with a supported, secure alternative.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Shibby Tomato versions 1.0 through 1.7 contain out-of-bounds write and memory corruption vulnerabilities.

Executive Summary:
Shibby Tomato firmware versions 1.0 through 1.7 are vulnerable to memory corruption and out-of-bounds write flaws, which may allow an authenticated attacker to compromise the device.

Vulnerability Details

CVE-ID: CVE-2026-15545

Affected Software: Shibby Tomato

Affected Versions: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7

Vulnerability: The firmware contains an out-of-bounds write (CWE-787) and memory corruption (CWE-119) vulnerability. These flaws can be triggered by an authenticated attacker, potentially leading to arbitrary code execution within the firmware's environment.

Business Impact

The CVSS score of 8.8 indicates a critical threat to network infrastructure. Exploitation could grant an attacker full control over the router or gateway device, allowing for traffic interception, network redirection, and persistent backdooring of the environment.

Remediation Plan

Immediate Action: Check the Shibby Tomato project repository for firmware updates and apply the latest stable version to address these memory corruption issues.

Proactive Monitoring: Monitor device logs for abnormal reboots or unauthorized configuration changes that could indicate a successful exploit.

Compensating Controls: Restrict administrative access to the router's management interface to trusted, known IP addresses only to reduce the attack surface.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Out-of-bounds write vulnerabilities in firmware are highly dangerous and often lead to complete device takeover.

Analyst Recommendation

Firmware security is paramount for network stability. Users must treat this vulnerability with high urgency and prioritize upgrading to the latest firmware release to secure the device against potential remote or local exploitation attempts.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Shibby Tomato firmware contains a stack-based buffer overflow vulnerability that allows authenticated attackers to corrupt memory and potentially execute arbitrary code.

Executive Summary:
A high-severity stack-based buffer overflow in Shibby Tomato firmware versions 1.0 through 1.7 exposes the system to potential remote code execution by authenticated users.

Vulnerability Details

CVE-ID: CVE-2026-15544

Affected Software: Shibby Tomato

Affected Versions: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7

Vulnerability: This vulnerability involves a stack-based buffer overflow (CWE-121) leading to memory corruption (CWE-119). The CVSS vector indicates that a low-privileged authenticated attacker (PR:L) can trigger this condition remotely.

Business Impact

Successful exploitation allows an attacker to gain control over the router or networking device, which could be used to compromise local network traffic or serve as a persistence mechanism. With a CVSS score of 8.8, the impact to confidentiality, integrity, and availability is high, necessitating urgent remediation or mitigation.

Remediation Plan

Immediate Action: Check the Shibby Tomato release channels for patched firmware versions and apply them to all affected devices.

Proactive Monitoring: Monitor system logs for signs of memory exhaustion or unexpected service crashes, which may indicate an attacker attempting to exploit the buffer overflow.

Compensating Controls: Implement strict network segmentation to ensure that only authorized personnel can access the administrative interface of the affected devices.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Stack-based overflows in firmware are critical as they often permit direct control over the execution flow of the device.

Analyst Recommendation

Users of Shibby Tomato firmware must treat this as a high-priority update. Until a patch is confirmed and applied, limit the exposure of the administrative interface to prevent unauthorized access and potential exploitation.

---METADATA---
VENDOR: Tenda
PRODUCT: CH22
AFFECTED_VERSIONS: 1.0.0.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A buffer overflow vulnerability in Tenda CH22 allows authenticated remote attackers to corrupt memory and potentially execute arbitrary code.

Executive Summary:
A high-severity memory corruption vulnerability in Tenda CH22 devices poses a significant risk of arbitrary code execution for authenticated attackers.

Vulnerability Details

CVE-ID: CVE-2026-15543

Affected Software: Tenda CH22

Affected Versions: 1.0.0.1

Vulnerability: The device is susceptible to a buffer overflow (CWE-120) and memory corruption (CWE-119) triggered via specific inputs. Based on the CVSS vector (PR:L), this vulnerability requires the attacker to be authenticated to the device to initiate the exploit.

Business Impact

A successful exploit could allow an attacker to execute arbitrary code with the privileges of the affected service, leading to full device compromise. Given the CVSS score of 8.8, this vulnerability represents a high risk to network integrity, potentially allowing lateral movement or the interception of traffic passing through the Tenda hardware.

Remediation Plan

Immediate Action: Contact Tenda support or monitor the official Tenda website for firmware updates addressing this memory corruption issue.

Proactive Monitoring: Review device access logs for unusual administrative activity and monitor for unexpected service restarts that may indicate crash-based exploitation attempts.

Compensating Controls: Restrict management interface access to trusted administrative IP addresses only to limit the pool of potential attackers who can authenticate and trigger the flaw.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the potential for memory corruption, which typically provides a reliable path to code execution once the initial authentication barrier is cleared.

Analyst Recommendation

The severity of this vulnerability necessitates immediate attention. Organizations utilizing Tenda CH22 devices should prioritize restricting management access and verifying firmware versions against the manufacturer's security bulletins as soon as they become available.

---METADATA---
VENDOR: will-moss
PRODUCT: Isaiah
AFFECTED_VERSIONS: 1.36.0, 1.36.1, 1.36.2, 1.36.3, 1.36.4, 1.36.5, 1.36.6, 1.36.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
An improper authentication vulnerability in will-moss Isaiah allows unauthenticated attackers to bypass authentication mechanisms.

Executive Summary:
An authentication bypass vulnerability in will-moss Isaiah allows unauthenticated attackers to gain unauthorized access to the application.

Vulnerability Details

CVE-ID: CVE-2026-15542

Affected Software: will-moss Isaiah

Affected Versions: 1.36.0, 1.36.1, 1.36.2, 1.36.3, 1.36.4, 1.36.5, 1.36.6, 1.36.7

Vulnerability: This vulnerability is categorized as Improper Authentication (CWE-287), where the application fails to correctly verify the identity of users, allowing unauthenticated remote access.

Business Impact

Successful exploitation allows an attacker to bypass the login process entirely, leading to full unauthorized access to the application's features and data. The CVSS score of 7.3 underscores the high risk of account takeover and potential loss of data confidentiality or system control.

Remediation Plan

Immediate Action: Audit current installations and monitor the vendor's GitHub repository for official security patches to resolve the authentication failure.

Proactive Monitoring: Review authentication logs for suspicious login activity or anomalous sessions that bypass standard login flows.

Compensating Controls: Utilize Web Application Firewalls (WAF) to filter out suspicious requests and restrict access to the application interface.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Authentication bypasses of this nature are high-value targets for attackers.

Analyst Recommendation

Authentication bypasses are critical security failures. Organizations using the affected versions of Isaiah must monitor for official remediation and apply updates immediately upon availability to secure the application's entry point.

---METADATA---
VENDOR: will-moss
PRODUCT: Isaiah
AFFECTED_VERSIONS: 1.36.0, 1.36.1, 1.36.2, 1.36.3, 1.36.4, 1.36.5, 1.36.6, 1.36.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A missing and incorrect authorization vulnerability in will-moss Isaiah allows unauthenticated attackers to perform unauthorized actions.

Executive Summary:
An authorization vulnerability in will-moss Isaiah exposes the application to unauthorized actions by unauthenticated attackers.

Vulnerability Details

CVE-ID: CVE-2026-15541

Affected Software: will-moss Isaiah

Affected Versions: 1.36.0, 1.36.1, 1.36.2, 1.36.3, 1.36.4, 1.36.5, 1.36.6, 1.36.7

Vulnerability: This flaw involves Missing (CWE-862) and Incorrect (CWE-863) Authorization, allowing an unauthenticated remote attacker to bypass security checks and perform restricted operations.

Business Impact

The exploitation of this vulnerability could lead to unauthorized access to sensitive application functions, potentially resulting in data manipulation or unauthorized configuration changes. With a CVSS score of 7.3, this high-severity flaw poses a significant risk to the integrity and availability of the affected system.

Remediation Plan

Immediate Action: Review the official will-moss GitHub repository for security patches or updated releases addressing these authorization flaws.

Proactive Monitoring: Monitor application access logs for unusual patterns, particularly unauthorized attempts to access administrative or restricted endpoints.

Compensating Controls: Implement strict network-level access controls or a Web Application Firewall (WAF) to restrict traffic to known, authorized IP addresses.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is fundamentally exploitable due to the absence of proper authorization checks on critical functions.

Analyst Recommendation

Given the high CVSS score and the nature of authorization bypasses, administrators should prioritize the identification of current deployments. Apply the necessary updates or security patches as soon as they are made available by the vendor to prevent unauthorized access.

---METADATA---
VENDOR: SourceCodester
PRODUCT: Online Book Store System
AFFECTED_VERSIONS: 1.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A SQL injection vulnerability in SourceCodester Online Book Store System v1.0 allows unauthenticated attackers to execute arbitrary SQL commands.

Executive Summary:
A critical SQL injection vulnerability in SourceCodester Online Book Store System allows unauthenticated attackers to compromise the backend database.

Vulnerability Details

CVE-ID: CVE-2026-15537

Affected Software: SourceCodester Online Book Store System

Affected Versions: 1.0

Vulnerability: This is a SQL Injection vulnerability (CWE-89) that permits unauthenticated remote attackers to manipulate database queries, leading to unauthorized data access or authentication bypass.

Business Impact

SQL injection is a severe risk that can lead to the complete compromise of the database, including sensitive user information and administrative credentials. With a CVSS score of 7.3, this vulnerability represents a significant threat to business continuity and data privacy.

Remediation Plan

Immediate Action: Since this is a legacy or open-source system, review the codebase to implement parameterized queries to mitigate SQL injection.

Proactive Monitoring: Monitor database query logs for unusual syntax or high volumes of error-generating requests indicative of injection attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) configured with SQL injection protection rules to block malicious payloads targeting the input fields.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. However, SQL injection vulnerabilities are frequently targeted due to their ease of exploitation once identified.

Analyst Recommendation

Given the high risk associated with SQL injection, administrators should prioritize sanitizing all user inputs within the application. If a formal patch is not provided by the vendor, custom remediation via code refactoring is essential to secure the database.

---METADATA---
VENDOR: Jinher
PRODUCT: OA
AFFECTED_VERSIONS: 1.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Jinher OA version 1.0 contains a SQL injection vulnerability that allows unauthenticated remote attackers to execute arbitrary database queries.

Executive Summary:
A critical SQL injection vulnerability in Jinher OA 1.0 exposes the application to unauthorized database manipulation and potential data exfiltration by unauthenticated attackers.

Vulnerability Details

CVE-ID: CVE-2026-15517

Affected Software: Jinher OA

Affected Versions: 1.0

Vulnerability: This is a SQL injection vulnerability (CWE-89) arising from insufficient input validation. The vulnerability is exploitable by unauthenticated remote attackers over the network.

Business Impact

Successful exploitation of this flaw allows attackers to interact directly with the backend database, potentially leading to the unauthorized disclosure or modification of sensitive organizational data. Given the CVSS score of 7.3, this represents a high-risk scenario where the confidentiality and integrity of the OA system are significantly compromised.

Remediation Plan

Immediate Action: Contact the vendor immediately to obtain the latest security patch. If no patch is available, restrict network access to the application to trusted IP addresses only.

Proactive Monitoring: Review database access logs for unusual query patterns, such as unexpected syntax or large data exports, which may indicate exploitation attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting input parameters.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. SQL injection flaws in OA software are high-value targets for attackers seeking to gain unauthorized access to internal business processes.

Analyst Recommendation

The severity of this vulnerability necessitates immediate attention. Administrators must prioritize identifying all instances of Jinher OA in their environment and applying vendor-supplied updates as soon as they become available to prevent potential system compromise.

---METADATA---
VENDOR: Tencent
PRODUCT: PC Manager
AFFECTED_VERSIONS: 18.1.30242.301
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Tencent PC Manager is susceptible to an uncontrolled search path vulnerability, potentially allowing local attackers to execute arbitrary code with elevated privileges.

Executive Summary:
An uncontrolled search path vulnerability in Tencent PC Manager 18 could allow a local attacker to achieve privilege escalation through malicious library loading.

Vulnerability Details

CVE-ID: CVE-2026-15515

Affected Software: Tencent PC Manager

Affected Versions: 18.1.30242.301

Vulnerability: This vulnerability involves an uncontrolled search path (CWE-427/CWE-426), where the application insecurely searches for dynamic link libraries. An authenticated local user (PR:L) can exploit this to load malicious code, provided they can influence the environment or search paths.

Business Impact

With a CVSS score of 7.0, this vulnerability presents a significant risk for environments where local system security is paramount. Successful exploitation allows for privilege escalation, potentially granting an attacker full control over the local system, leading to complete compromise of the host machine and potential lateral movement within the network.

Remediation Plan

Immediate Action: Monitor vendor communication channels for the release of a security patch and apply it as soon as it becomes available.

Proactive Monitoring: Audit local system logs for unexpected file executions or DLL loading patterns that originate from non-standard or user-writable directories.

Compensating Controls: Restrict local user permissions and ensure that system folders and application directories have strict Access Control Lists (ACLs) to prevent unauthorized file placement.

Exploitation Status

Public Exploit Available: Yes — a GitHub repository exists (subsubsub1231/qmukiller).

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation in the wild; however, a proof-of-concept repository is publicly available, making the risk of exploitation credible. The vulnerability's reliance on local access and specific path configurations makes it a targeted risk for local privilege escalation.

Analyst Recommendation

Due to the availability of a public proof-of-concept and the high impact of privilege escalation, administrators should restrict local access to the affected systems. Ensure that the Tencent PC Manager software is updated to the latest available version as soon as the vendor issues a fix to resolve the search path vulnerability.

---METADATA---
VENDOR: Metasoft
PRODUCT: MetaCRM
AFFECTED_VERSIONS: 6.4.0 Beta06
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Metasoft MetaCRM version 6.4.0 Beta06 contains a SQL injection vulnerability that allows unauthenticated remote attackers to execute arbitrary database commands.

Executive Summary:
A critical SQL injection vulnerability in Metasoft MetaCRM 6.4.0 Beta06 poses a significant risk of unauthorized data access and system compromise by unauthenticated attackers.

Vulnerability Details

CVE-ID: CVE-2026-15514

Affected Software: Metasoft MetaCRM

Affected Versions: 6.4.0 Beta06

Vulnerability: This vulnerability is a SQL injection (CWE-89) flaw resulting from improper neutralization of special elements in input parameters. The vulnerability is accessible to unauthenticated remote attackers via network vectors.

Business Impact

The ability to perform SQL injection allows an attacker to bypass authentication and access sensitive CRM data, potentially leading to a major data breach. With a CVSS score of 7.3, this vulnerability requires urgent remediation to protect the confidentiality and integrity of customer and business information stored within the CRM.

Remediation Plan

Immediate Action: Verify if a production-ready update is available beyond the Beta version. If the software is currently in use, isolate the system from public-facing networks until a patch is applied.

Proactive Monitoring: Monitor application logs for signs of SQL injection attempts and anomalous traffic originating from external sources.

Compensating Controls: Implement WAF rules to filter malicious SQL strings and perform rigorous input validation at the application level where possible.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Beta versions often lack the security hardening of production releases, increasing the risk of such flaws.

Analyst Recommendation

Organizations utilizing Metasoft MetaCRM should treat this as a high-priority incident. Given the nature of CRM systems holding sensitive data, it is recommended to restrict access to the application and coordinate directly with the vendor for a security update to address this injection flaw.

---METADATA---
VENDOR: Comfast
PRODUCT: CF-WR631AX V3
AFFECTED_VERSIONS: 2.7.0.0, 2.7.0.1, 2.7.0.2, 2.7.0.3, 2.7.0.4, 2.7.0.5, 2.7.0.6, 2.7.0.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A critical OS command injection vulnerability exists in the Comfast CF-WR631AX V3 router via the FastCGI backend, allowing unauthenticated remote attackers to execute arbitrary system commands.

Executive Summary:
A critical OS command injection vulnerability in the Comfast CF-WR631AX V3 router allows unauthenticated remote attackers to execute arbitrary system commands, posing a severe risk of full device compromise.

Vulnerability Details

CVE-ID: CVE-2026-15511

Affected Software: Comfast CF-WR631AX V3

Affected Versions: 2.7.0.0, 2.7.0.1, 2.7.0.2, 2.7.0.3, 2.7.0.4, 2.7.0.5, 2.7.0.6, 2.7.0.7

Vulnerability: The flaw exists in the system_wl_upload_pic_file function within the /usr/bin/webmgnt binary. An unauthenticated attacker can supply a malicious filename to trigger OS command injection.

Business Impact

Successful exploitation allows an attacker to gain full control over the router, potentially leading to unauthorized network access, data interception, or the device being utilized as a pivot point for lateral movement within the enterprise network. With a CVSS score of 9.8, this vulnerability represents an extreme risk to infrastructure integrity and confidentiality.

Remediation Plan

Immediate Action: As no official patch is currently available, restrict access to the web management interface of the affected routers to trusted administrative IP addresses only.

Proactive Monitoring: Monitor network traffic for unusual outbound connections from the router and review system logs for attempts to call unexpected shell commands.

Compensating Controls: If possible, place the management interface behind a firewall or VPN to ensure it is not reachable by unauthorized external actors.

Exploitation Status

Public Exploit Available: Yes — a public proof-of-concept exists on GitHub.

Analyst Notes: As of July 12, 2026, there is no confirmed active exploitation in the wild; however, a public proof-of-concept repository is available, making the exploitation risk highly credible. The vulnerability's lack of authentication requirements makes it a prime target for automated exploitation.

Analyst Recommendation

Due to the critical nature of this command injection flaw and the availability of public exploit code, immediate segmentation of the management interface is mandatory. Organizations should prioritize replacing these devices if the vendor fails to release a security update in a timely manner.

---METADATA---
VENDOR: SecureAge
PRODUCT: CatchPulse
AFFECTED_VERSIONS: 10.9.0, 10.9.1, 10.9.2, 10.9.3
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
SecureAge CatchPulse versions 10.9.0 through 10.9.3 contain heap-based buffer overflow and memory corruption vulnerabilities.

Executive Summary:
Multiple memory corruption vulnerabilities in SecureAge CatchPulse versions 10.9.0-10.9.3 could allow an authenticated local attacker to achieve code execution or system instability.

Vulnerability Details

CVE-ID: CVE-2026-15506

Affected Software: SecureAge CatchPulse

Affected Versions: 10.9.0, 10.9.1, 10.9.2, 10.9.3

Vulnerability: The software is susceptible to heap-based buffer overflows (CWE-122) and general memory corruption (CWE-119). These flaws require low-privilege local access to trigger, potentially leading to privilege escalation or service crashes.

Business Impact

With a CVSS score of 7.8, this vulnerability poses a significant risk to endpoint security. If exploited, an attacker could compromise the integrity and availability of the host machine, bypassing security controls managed by the CatchPulse software.

Remediation Plan

Immediate Action: Contact SecureAge support or monitor their official portal for a security update addressing these memory corruption flaws and apply the patch as soon as it is released.

Proactive Monitoring: Monitor endpoint logs for application crashes or unusual system behavior that may indicate an exploitation attempt targeting the CatchPulse service.

Compensating Controls: Ensure that local user permissions are strictly managed and restricted to prevent unauthorized interaction with security-critical software components.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The nature of memory corruption flaws often makes them candidates for weaponization in local privilege escalation chains.

Analyst Recommendation

The reliance on memory-safe operations is critical for security software. Users of the affected versions should transition to a patched version immediately once provided by the vendor to prevent potential local exploitation.

---METADATA---
VENDOR: sergomanov
PRODUCT: SmartHomeAdatum
AFFECTED_VERSIONS: up to commit cf495353d81b680675eb8d9aa14a318aa45ce12c
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A SQL injection vulnerability exists in the sergomanov SmartHomeAdatum Login component (users.php), allowing unauthenticated attackers to potentially access or manipulate database information.

Executive Summary:
An unauthenticated SQL injection vulnerability in sergomanov SmartHomeAdatum allows for potential unauthorized database access.

Vulnerability Details

CVE-ID: CVE-2026-15498

Affected Software: sergomanov SmartHomeAdatum

Affected Versions: up to commit cf495353d81b680675eb8d9aa14a318aa45ce12c

Vulnerability: This vulnerability consists of SQL injection (CWE-89) and general injection (CWE-74) flaws within the users.php file of the Login component. The vulnerability is accessible to unauthenticated remote attackers.

Business Impact

With a CVSS score of 7.3, this vulnerability represents a High severity risk. Successful exploitation could lead to unauthorized access to the underlying database, data exfiltration, or modification of application state. Because SmartHomeAdatum follows a rolling release model without discrete versioning, users are at persistent risk until the upstream source code is updated.

Remediation Plan

Immediate Action: Since no formal patch is available, administrators should audit the users.php file and implement input sanitization and parameterized queries to neutralize the injection vector.

Proactive Monitoring: Monitor application logs for SQL syntax errors or unexpected database queries that might indicate an active injection attempt.

Compensating Controls: Deploy a Web Application Firewall (WAF) with SQL injection protection rules to block malicious payloads targeting the login interface.

Exploitation Status

Public Exploit Available: No (unknown)

Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous as it allows for direct interaction with the database.

Analyst Recommendation

Due to the lack of an official patch and the nature of SQL injection, users of SmartHomeAdatum should immediately restrict access to the login interface. If the functionality is not business-critical, consider disabling the affected component until the upstream repository provides a security update.