Reserved but Public CVEs

CVE-2024-45747 is a server-side template injection vulnerability in GeoServer's FreeMarker template processing. The flaw allows an authenticated administrator to supply or influence FreeMarker template content in a way that exposes unsafe template capabilities, enabling execution of operating system commands and arbitrary file read or write operations on the underlying server. The issue stems from insufficient restriction of objects and API access available to FreeMarker templates during server-side rendering.

CVE-2024-45747First seen Aug 20, 2026

First seen Aug 19, 2026

CVE-2026-21541First seen Jul 30, 2026

CVE-2025-48557First seen Jul 30, 2026

CVE-2025-47100First seen Jul 30, 2026

CVE-2026-21543First seen Jul 30, 2026

CVE-2024-54052First seen Jul 30, 2026

CVE-2026-21544First seen Jul 30, 2026

CVE-2024-54033First seen Jul 30, 2026

CVE-2026-21538First seen Jul 30, 2026

CVE-2026-28574First seen Jul 30, 2026

CVE-2026-21546First seen Jul 30, 2026

CVE-2025-26447First seen Jul 30, 2026

CVE-2026-21539First seen Jul 30, 2026

CVE-2026-21542First seen Jul 30, 2026

CVE-2026-21545First seen Jul 30, 2026

CVE-2026-21540First seen Jul 30, 2026

CVE-2026-21547First seen Jul 30, 2026

CVE-2023-37465 is a cross-site request forgery vulnerability in the XWiki Discussion Extension component org.xwiki.contrib:discussions-server. The flaw allows an attacker to cause a victim's browser to submit a forged request to the application, resulting in deletion of discussion messages. The issue affects the server-side discussion functionality prior to version 2.0-rc-1.

CVE-2023-37465First seen Jul 28, 2026

CVE-2026-59766 is an access control flaw in Gitea caused by an incomplete fix for CVE-2026-20800. After a user's access to a private repository is revoked, the user can still retrieve information through the authenticated API endpoints that list starred repositories and personal tracked-time entries. Specifically, the /api/v1/user/starred endpoint can continue to disclose metadata for private repositories the user had previously starred, and the /api/v1/user/times endpoint can continue to disclose private issue titles associated with time entries previously logged by that user. Exposed information includes repository metadata such as repository objects, clone and SSH URLs, privacy status, issue titles, and issue state. Available information indicates that repository contents and issue comment bodies are not exposed.

CVE-2026-59766First seen Jul 22, 2026

CVE-2026-57118 is an improper authentication vulnerability in PraisonAI praisonaiagents affecting the HTTP endpoints exposed by AgentTeam.launch() and Agents.launch(). When these launch functions are used to expose agent services over the network, externally reachable endpoints permit unauthenticated clients to list deployed agents and invoke team-level or per-agent execution functionality. The issue stems from network-facing functionality being exposed without requiring authentication, allowing remote parties to interact with agent orchestration features that should be access-controlled.

CVE-2026-57118First seen Jul 21, 2026

CVE-2026-57121 is an improper authorization vulnerability in PraisonAI Platform affecting versions starting at 0.1.4 and fixed in 0.1.6. The API's DELETE endpoints fail to enforce ownership or privileged-role authorization checks, allowing any authenticated workspace member to delete resources created by other workspace members or by the workspace owner. Affected resource types include projects, agents, issues, labels, issue dependencies, and issue-label attachments. The flaw stems from missing server-side validation that the requester is either the resource owner or holds an administrative role before destructive actions are permitted.

CVE-2026-57121First seen Jul 21, 2026

CVE-2026-56834 is an arbitrary file read vulnerability in PraisonAI Dynamic Context Discovery artifact tools. The flaw allows artifact operations to access host files outside the configured artifact storage boundary when an attacker can influence artifact tool arguments. The vulnerable design relies on raw filesystem path handling rather than strict artifact identifier resolution and insufficiently enforces containment within the configured artifact store base directory. Affected artifact helper operations include file access and content inspection functions such as load, head, tail, grep, chunk, and delete unless equivalent validation is applied. Successful exploitation enables unauthorized reading of local files accessible to the PraisonAI process, resulting in exposure of sensitive data from the host environment.

CVE-2026-56834First seen Jul 21, 2026

CVE-2026-56838 is a policy enforcement flaw in PraisonAI in which recipe.run_stream() does not apply the dangerous-tool restrictions enforced by recipe.run(). As a result, recipes executed through the streaming code path can declare and invoke dangerous tools, including command-execution capabilities, despite the default denial model intended to block such use. The issue stems from inconsistent security checks between non-streaming and streaming execution paths, allowing the streaming interface to bypass the intended preflight validation and authorization boundary for dangerous tools.

CVE-2026-56838First seen Jul 21, 2026

CVE-2026-57210 is an IP spoofing vulnerability in Heimdall caused by insufficient validation of client-supplied Forwarded and X-Forwarded-For headers when trusted_proxies is configured. Under affected configurations, malformed or attacker-controlled header values can be accepted into client IP address handling and used to populate Request.ClientIPAddresses. This can influence rule evaluation that relies on client IP information and, in proxy mode, can also cause spoofed or malformed client IP data to be propagated to upstream services.

CVE-2026-57210First seen Jul 21, 2026