CVE Vulnerability Catalog

DiscordChatExporter before 2.47.2 saves Discord chat logs to a file. The VisitEmojiAsync method in DiscordChatExporter.Core/Exporting/HtmlMarkdownVisitor.cs interpolates emoji.Name into the alt attribute and emoji.Code into the title attribute without HTML entity encoding. This affects HTML exports regardless of the markdown setting. Discord's current custom emoji name validation normally excludes attribute-breaking characters, but tampered offline input, a relaxed upstream validation rule, or another future metadata source can inject an HTML attribute and execute script when a user opens the export.

OctoPrint before versions 1.11.8 and 2.0.0rc3 has a parsing discrepancy between its custom Tornado upload handler and Flask/Werkzeug, allowing an attacker with FILE_UPLOAD permission to inject reserved internal upload fields via query parameters or parser differentials. Affected endpoints include /api/files/{local|sdcard}, /api/languages, /plugin/backup/restore, and /plugin/pluginmanager/upload_file.

VeraCrypt from 1.26.6 until 1.26.29, file-hosted hidden volume creation forces quick format and the FormatNoFs function in src/Common/Format.c and FormatFat function in src/Common/Fat.c use WriteFile to place raw zeroed sectors at predictable 128 MiB intervals. These writes bypass the normal EncryptDataUnits formatting path, leaving deterministic plaintext markers in an area expected to resemble random ciphertext. The markers can weaken plausible deniability during forensic inspection, although they do not disclose hidden-volume content or reduce the strength of VeraCrypt encryption.

BabelDOC before version 0.6.3 has a vendored PDF parser in babeldoc/pdfminer/cmapdb.py that deserializes untrusted pickle data when CMapDB._load_data() loads CMap files. PDF-controlled Encoding or CMapName values and embedded PostScript usecmap operators can reach this sink after path separators are decoded, while _normalize_cmap_name() removes only a leading slash.

In VeraCrypt prior to 1.26.29, non-default builds created with WOLFCRYPT=1 and WOLFCRYPT_BACKEND route SHA-256 and SHA-512 volume-header key derivation through derive_key_sha256 and derive_key_sha512 in src/Crypto/wolfCrypt.c, where the configured iterations value is discarded and wc_HKDF is used instead of PBKDF2-HMAC. Changing the PIM or iteration count therefore does not increase derivation cost, allowing an attacker with an affected container, disk image, or volume header to perform substantially cheaper offline password guesses. Official precompiled VeraCrypt binaries and normal distribution packages use the standard PBKDF2 backend and are not affected. Volumes created by an affected WOLFCRYPT=1 build require backup and recreation because corrected builds derive different keys.

OctoPrint prior to 1.11.8 and 2.0.0rc3, Suppressed Command notification popups use PNotify rendering for printer-controlled payload.command and payload.message values in src/octoprint/static/js/app/viewmodels/terminal.js without HTML escaping. An attacker who convinces a victim to print a crafted file can inject HTML and JavaScript into the notification, disrupt prints, read information available to the victim including sensitive settings when permitted, or perform actions in the victim's OctoPrint session.

Missing queue-set type validation in xQueueAddToSet() in the FreeRTOS-Kernel before 11.3.1 might allow an unprivileged task on MPU-enabled ports with configUSE_QUEUE_SETS=1 to read privileged kernel memory. To remediate this issue, users should upgrade to version 11.3.1 or later.

FreeRTOS-Kernel before version 11.3.1 lacks minimum size validation in secure context allocation, which might allow local users to corrupt secure-world heap metadata via an out-of-bounds write with an undersized stack size parameter.

FreeRTOS-Kernel before version 11.3.1 lacks privilege verification in the secure context cleanup handler, which might allow local users to cause a use-after-free condition in secure-world memory via the SVC handler for secure context deallocation.

FreeRTOS-Kernel before version 11.3.1 has improper input validation, which might allow an unprivileged task on MPU-enabled ports to execute code in privileged kernel context.

Checkmate from version 3.3.0 until 3.9.2, when the global showURL setting is enabled, causes the unauthenticated GET /api/v1/status-page/:url endpoint to return complete monitor objects, including the secret field used as an HTTP Authorization credential, even though it is not displayed in the UI.

Infracost prior to 0.10.45, internal/hcl/remote_variables_loader.go and related Terraform Cloud, remote-plan, and Terragrunt registry request paths can attach a configured Terraform Cloud or registry token to a destination hostname derived from untrusted Terraform input without confirming that it is the configured trusted host. When a CI run provides a token while scanning attacker-controlled Terraform, including pull_request_target or a same-repository pull request, an attacker can direct the request to an attacker-controlled host and disclose the token. Standard fork pull_request workflows without secrets are not exposed.

Prior to version 0.10.45, Infracost had a vulnerability where the template functions readFile, pathExists, isDir, and matchPaths did not resolve intermediate directory symlinks. A repository could contain a path such as evil/file where evil points outside the checkout, causing os.ReadFile and related operations to follow the symlink and read runner-accessible files. The resulting content could be rendered into generated configuration and surfaced through the Infracost dashboard or pull request comment, with greater impact in workflows that provide repository secrets.

In Checkmate versions from 3.5.1 to 3.9.2, an authenticated admin or superadmin can set matchMethod to regex and place a malicious expression in the expectedValue field for advanced HTTP monitor matching. The expression is synchronously evaluated on the Node.js main event loop without a timeout or worker isolation, allowing catastrophic backtracking to freeze API endpoints, monitor checks, and WebSocket connections for all users. This issue is fixed in version 3.9.2.

Omnigent before version 0.3.0 allows an authenticated user to upload a session-scoped agent bundle with an absolute or traversal-containing os_env.cwd value because the parser stores the value verbatim and the validator does not constrain it. When OMNIGENT_RUNNER_WORKSPACE is unset, an attacker can control the path and gain access to runner files and environment secrets outside the intended workspace.

Omnigent before version 0.3.0 has a shared shell-command parser that fails to recognize combined interpreter flags, timeout, nice, setsid, and stdbuf wrappers, command substitutions, and a single background control operator. Commands hidden with these forms produce no parsed operation, causing allowlist and workspace confinement policies to abstain and allow the command.

Omnigent before version 0.3.0 accepts an agent bundle in multipart POST /v1/sessions, and the validator does not reject a dotted Python path in tools..callable. The dispatcher imports the specified module and invokes the function, allowing a bundle to select subprocess.check_output and execute a local command with the runner process permissions.

Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, PUT /sessions/{session_id}/agent checks LEVEL_EDIT permission for a session but does not reject a bound shared or template agent whose agent.session_id is None. An authenticated user with edit access to a session can replace that shared agent bundle through omnigent/server/routes/sessions.py, add a stdio MCP server, and cause later sessions that use the shared agent to launch an attacker-controlled command through omnigent/tools/mcp.py. The command executes with the Omnigent runner process permissions and can expose files, credentials, workspace data, internal services, and runner availability. This issue is fixed in version 0.3.0.

Checkmate before version 3.9.1 has a memory exhaustion vulnerability in the public registration endpoint. An unauthenticated attacker can send multiple concurrent oversized files that are buffered before validation, leading to memory exhaustion and backend crash.

UAC before version 3.3.0 has a command injection vulnerability in the user substitution logic in parse_artifact.sh. Usernames and home directories from /etc/passwd are substituted into command strings without proper escaping before execution via eval, allowing injection of shell metacharacters.