Skip to content
OpenAdvisories

Archive

August 2026

Vulnerabilities first published in this month (UTC), newest first.

12,374 results · Feed

  • Medium 4.7

    Heap-based Buffer Overflow in Wireshark

    Catapult DCT2000 file parser crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

  • Medium 4.7

    Out-of-bounds Read in Wireshark

    Bluetooth Attribute Protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

  • Medium 4.7

    NULL Pointer Dereference in Wireshark

    CMS protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

  • High 8.4

    In OpenStack Aodh before 22.0.1, the alarm list API bypasses project scoping when the all_projects query parameter is s…

  • High 7.4

    TRENDnet TEW-755AP ssi email.cgi log_email_server command injection

    A security flaw has been discovered in TRENDnet TEW-755AP up to 20260702. This affects the function log_email_server of the file /cgi-bin/email.cgi of the component ssi. Performing a manipulation results in command injection. The attack is possible to be carr…

  • High 8.8

    Agno PythonTools Path Traversal via joinpath file_name argument

    Agno's PythonTools in libs/agno/agno/tools/python.py contains a path traversal vulnerability that allows attackers to read, write, or execute arbitrary files by supplying parent-directory traversal sequences in the file_name argument passed to read_file, save…

  • Critical 9.9

    TRENDnet TEW-755AP ssi wan.cgi stack-based overflow

    A vulnerability was identified in TRENDnet TEW-755AP up to 20260702. Affected by this issue is some unknown functionality of the file /cgi-bin/wan.cgi of the component ssi. Such manipulation of the argument cameo.wan.wan_pppoe_password_00 leads to stack-based…

  • Critical 9.8

    LMDeploy Remote Code Execution via Unsafe Pickle Deserialization in the Disaggregated Serving Peer Connector

    LMDeploy deserializes disaggregated-serving peer messages with pickle. The handle_zmq_recv coroutine in lmdeploy/pytorch/disagg/conn/engine_conn.py reads peer-to-peer cache-free requests with recv_pyobj(), which deserializes the received bytes with pickle.loa…

  • Medium 6.5

    Tina: Cross-origin `POST /media/upload/*` requests can write arbitrary files into the Tina dev server media root

    Tina is a headless content management system. Prior to 2.5.2, the TinaCMS CLI package's Vite dev server packages/@tinacms/cli/src/next/vite/cors.ts origin callback returns false for a disallowed origin but does not reject the request, and packages/@tinacms/cl…

  • Medium 4.3

    Information Disclosure through Cleartext Storage in the App Key Value Store in the Splunk On-Call (VictorOps) app

    In Splunk On-Call (VictorOps) app versions below 1.0.43 on Splunkbase, a user who does not hold the "admin" or "power" Splunk roles could read a partially masked Application Programming Interface (API) key from the App Key Value Store (KV Store). The exposure…

  • Critical 9.1

    Remote Code Execution (RCE) through Deserialization of Untrusted Data in Splunk MCP Server app

    In Splunk MCP Server app versions below 1.2.1, a user who holds the "admin" Splunk role could execute arbitrary commands on the underlying operating system. The vulnerability is possible because of missing input validation in the app's credential management c…

  • High 7.4

    Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka

    In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user positioned in the network path could read or alter all relevant data sent from the connector when Kerberos authentication is used with Hypertext Transfer Protocol (HTTP) Event Collector…

  • High 8.2

    Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka

    In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure a non-secure Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterprise …

  • Medium 5.9

    Denial of Service (DoS) through the REST API in Splunk Connect for Kafka

    In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API and influence responses from a Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterpris…

  • Medium 5.9

    Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka

    In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure timestamp extraction with a crafted regular expression and matching event data to block a Kafk…

  • High 8.1

    Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.1, a user who holds the "power" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relev…

  • High 8.1

    Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not p…

  • Medium 4.3

    Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the "admin" or "power" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possibl…

  • High 8.8

    Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a mo…

  • High 7.5

    Improper Access Control through Scheduled Searches in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splun…

  • High 8.3

    Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the "admin" or "power" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfe…

  • Medium 5.4

    Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit g…

  • Medium 5.9

    Race Condition during Model Upload through the REST API in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-contr…

  • High 8.3

    Improper Privilege Management through Agent Run History in Splunk AI Toolkit

    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users…

  • Medium 5.3

    Information Disclosure through Splunk Web in Cisco Talos Intelligence for Enterprise Security Cloud

    In Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3, an unauthenticated user could access the add-on OpenAPI specification through Splunk Web static file paths. The exposed specification could allow for reconnaissance of the add-on …

  • High 8.8

    Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for Enterprise Security Cloud

    In Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3, a user that holds a role with the get_talos_enrichment capability could send a crafted request to the Talos intelligence enrichment Representational State Transfer (REST) API endp…

  • High 8.1

    Privilege Escalation through Search Macro Permissions in Splunk Enterprise Security

    In Splunk Enterprise Security versions below 8.6.1, a user who holds the ess_analyst Splunk Enterprise Security role could change User and Entity Behavior Analytics (UEBA) search macros that scheduled searches run with administrator permissions, allowing for …

  • High 8.1

    SPL Injection through the REST API in Splunk Enterprise Security

    In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read capability could inject Search Processing Language (SPL) through Analyst Queue search filters, allowing for access t…

  • Medium 4.3

    Information Disclosure through Action Parameters in Zoom app for Splunk SOAR

    In versions below 3.2.2 of the Zoom app for Splunk SOAR, a user who holds a role with permission to run actions could expose meeting and personal meeting ID passwords by invoking one of the create meeting, update meeting, or update user settings actions, beca…

  • Medium 4.3

    Information Disclosure through Action Parameters in Venafi app for Splunk SOAR

    In versions below 2.1.4 of the Venafi app for Splunk SOAR, a user who holds a role with permission to run actions could expose keystore and private-key passwords by invoking the get certificate action, because the action's keystore_password and password param…

  • Medium 4.3

    Information Disclosure through Action Parameters in Splunk Attack Analyzer Connector for Splunk SOAR

    In versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive archive password by invoking either the detonate file or detonate url action, because the action's…

  • Medium 4.3

    Information Disclosure through Action Parameters in Phantom app for Splunk SOAR

    In versions below 3.8.5 of the Phantom app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive archive password by invoking the deflate item action, because the action's password parameter is not masked and is show…

  • Medium 4.3

    Information Disclosure through Action Parameters in RSA SecurID Authentication Manager app for Splunk SOAR

    In versions below 1.0.5 of the RSA SecurID Authentication Manager app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive token serial by invoking either the enable token or revoke token action, because the action'…

  • Medium 4.3

    Information Disclosure through Action Parameters in CrowdStrike OAuth API app for Splunk SOAR

    In versions below 5.1.3 of the CrowdStrike OAuth API app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive document password by invoking either the detonate file or detonate url action, because the action's docum…

  • Medium 4.3

    Information Disclosure through Action Parameters in MS Graph for Active Directory app for Splunk SOAR

    In versions below 1.5.2 of the MS Graph for Active Directory app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive password by invoking the reset password action, because the action's temp_password parameter is n…

  • Medium 4.3

    Information Disclosure through Action Parameters in Cisco Webex app for Splunk SOAR

    In versions below 2.2.1 of the Cisco Webex app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive meeting password by invoking the schedule meeting action, because the action's password parameter is not masked and…

  • Medium 4.3

    Information Disclosure through Action Parameters in Azure AD Graph app for Splunk SOAR

    In versions below 2.5.3 of the Azure AD Graph app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive password by invoking the reset password action, because the action's temp_password parameter is not masked and i…

  • Medium 4.3

    Information Disclosure through Action Parameters in Cisco Secure Malware Analytics app for Splunk SOAR

    In versions below 2.4.5 of the Cisco Secure Malware Analytics app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive sample password by invoking the detonate file action, because the action's sample_password param…

  • Medium 5.0

    Information Disclosure through Environment Data Logging in AD LDAP app for Splunk SOAR

    In versions below 2.3.8 of the AD LDAP app for Splunk SOAR, a user who holds a role with permission to run actions could expose sensitive credentials by invoking an action that causes the full connector process environment to be written to a persistent debug …

  • Medium 4.3

    Information Disclosure through Action Parameters in AWS IAM app for Splunk SOAR

    In versions below 2.1.9 of the AWS IAM app for Splunk SOAR, a user who holds a role with permission to run actions could expose sensitive AWS credentials by invoking an action that accepts the credentials parameter, because the parameter is not masked and is …