CVE Vulnerability Catalog

Data::Intern::Shared versions before 0.02 for Perl allow an out-of-bounds read via unvalidated slot, reverse and arena indices in si_idx_find. The attach-time validator si_validate_header is thorough about the header and layout but does not validate the three arrays it then trusts. A local peer that can write the backing file can leave the header valid while poisoning a slot id, a reverse offset or an arena length prefix, so an id_of, intern or string lookup dereferences the chain out of bounds; because string() returns a file-controlled length of bytes from the arena, adjacent process memory can be disclosed.

The Data::RingBuffer::Shared module for Perl before version 0.04 contains a stack buffer overflow via an unvalidated elem_size in ring_read_seq. The ring_read_seq function copies data of size elem_size (read from an mmap'd file) into a fixed 8-byte destination buffer, potentially leading to stack-based write.

An issue in DayuanJiang next-ai-draw-io version 0.4.13 allows a remote attacker to obtain sensitive information via the X-Forwarded-For header.

Perl module Data::HashMap::Shared before version 0.14 contains an out-of-bounds read vulnerability via unvalidated arena offset and length in shm_str_copy. A local user who can write the backing file can poison records, leading to reading adjacent memory or process crash.

Perl module Data::RadixTree::Shared before version 0.02 contains an out-of-bounds read vulnerability via unvalidated node and arena indices in rdx_find_locked. A local user who can write the backing file can poison node records, leading to out-of-bounds read or process crash.

Perl module Data::SortedSet::Shared before version 0.03 contains an out-of-bounds read vulnerability via unvalidated node indices in rank, min, and max queries. A local user who can write the backing file can poison tree links, leading to out-of-bounds read or process crash.

Vulnerability in Data::ReqRep::Shared for Perl before version 0.05 allows an out-of-bounds read via an unvalidated arena offset and length. The validator does not check array contents, allowing a local attacker to manipulate the file and read adjacent memory or crash the process.

In Eclipse OpenJ9 up to version 0.60, when executing class files where a previously concrete superclass method has been recompiled as abstract, execution is incorrectly delegated to an interface default method.

Linknat VOS3000 and VOS2009 up to version 2.1.2.0 contain an unauthenticated SQL injection vulnerability. Attackers can execute arbitrary SQL commands via the name parameter in a POST request to the login endpoint and retrieve data with DBA privileges.

PraisonAI Platform versions prior to 0.1.4 have a privilege escalation vulnerability in the PATCH /workspaces/{workspace_id}/members/{user_id} endpoint. There is no caller permission check, allowing a user with the 'member' role to change any member's role, including their own, to 'owner'.

PraisonAI Platform versions prior to 0.1.4 have a privilege escalation and cross-tenant member injection vulnerability. The POST /workspaces/{workspace_id}/members endpoint lacks caller permission checks, allowing a user with the lowest role to add any user as an owner of the workspace.

Vulnerability in Eclipse OpenJ9 up to version 0.60. Using -Xtrace to trace method arguments can lead to buffer underflow.

PraisonAI Platform versions prior to 0.1.4 use a hardcoded default JWT secret 'dev-secret-change-me' when PLATFORM_JWT_SECRET is unset. The safety check is bypassed because PLATFORM_ENV defaults to 'dev'. An attacker can read the secret from a public source file, forge a JWT with arbitrary claims, and authenticate as any user, including admins.

PraisonAI Platform before version 0.1.4 has a vulnerability due to missing verification of resource ownership within workspaces in API endpoints. A user who is a member of one workspace can access resources of another workspace by manipulating the URL path. Additionally, the role hierarchy is not enforced in member management, allowing a basic member to escalate privileges to admin or owner.

Home Assistant Core before version 2026.6.0 contains a path traversal vulnerability that allows unauthenticated attackers to write arbitrary files to any directory on the host filesystem by uploading a crafted backup archive during the initial onboarding window. Attackers can manipulate the 'name' field inside the uploaded archive's backup.json to supply an absolute path, causing pathlib.Path.__truediv__ to discard the configured backup directory prefix and write attacker-controlled content to arbitrary locations, with full filesystem access when the process runs as root.

PraisonAI prior to version 4.6.40 exposes an unauthenticated agent control API when CALL_SERVER_TOKEN is not set. The verify_token() helper fails open, and the call server binds to 0.0.0.0 by default, allowing any client to list, inspect, invoke, and unregister agents.

PraisonAI by default generates a Flask API server without authentication, listening on all network interfaces (0.0.0.0) and exposing sensitive endpoints. An attacker can send requests to /chat and /agents endpoints without any authentication, allowing execution of LLM code with API keys present in the environment.

In PraisonAI before version 4.6.40 (corresponding to praisonaiagents version 1.6.40), a vulnerability exists in the `execute_code()` function in `praisonaiagents/tools/python_tools.py`. An attacker can bypass the subprocess sandbox by using `print.__self__` to access the real Python `builtins` module, then extract `__import__` via `vars()` and runtime string construction, achieving arbitrary OS command execution on the host.

PraisonAI before version 4.6.40 includes an example A2A server that exposes an unauthenticated A2A JSON-RPC endpoint and registers a calculate(expression) tool implemented with Python eval(). The server binds to 0.0.0.0. A remote unauthenticated attacker can send message/send to /a2a, causing the LLM to invoke the calculate tool, leading to arbitrary Python execution on the server. The vulnerability affects deployments following the official A2A example or similar unauthenticated A2A deployments with unsafe tools.

SolarWinds Serv-U suffers from a broken access control vulnerability that allows arbitrary file read/write, privilege escalation, and code execution as root. Domain administrator access is required; impact is lower on Windows.