Immich versions prior to 3.2.0 contain an improper authorization vulnerability in the shared-link creation API. An authenticated attacker who knows a victim's asset UUID could create a shared link that exposes the victim's asset without proper authorization. This results in unauthorized access to victim metadata, thumbnails, and original files through an anonymous shared link. The issue is fixed in version 3.2.0.
Immich versions prior to 3.0.0 contain an authorization bypass vulnerability allowing view-only partners to enumerate GPS coordinates and existence of archived photos or videos shared by others. This exposure is limited to location metadata and asset identifiers; the actual image data remains protected. The issue is resolved in version 3.0.0.
Immich versions prior to 3.3.0 contain a path traversal vulnerability in the unauthenticated /predict endpoint of the machine-learning component. This flaw allows an attacker with network access to specify an arbitrary writable path for cache_dir, potentially leading to deletion of attacker-selected directories or modification of files via clear_cache() after model-loading failures. The vulnerability is mitigated by a model-name allowlist that prevents arbitrary model deserialization or code execution. The issue is fixed in version 3.3.0.
In Secret Server versions earlier than 12.3.1, a user could bypass the initial login step and authenticate by successfully negotiating the second factor login step only.
In Secret Server versions earlier than 12.3.1, a user under certain conditions could submit an unsigned JWT and receive cloudadmin permissions in response.
A critical improper privilege management vulnerability (CWE-269) exists in akuity kargo versions from 0.6.0 up to but not including 1.8.14, 1.9.9, and 1.10.8. Authenticated users with delegated permission to manage a Project's Roles or ServiceAccounts can escalate their privileges beyond their own permissions. This allows escalation to Project-administrator access, disclosure of Project secrets and credentials, and modification or deletion of Project resources. Exploitation requires an administrator-created custom role granting relevant permissions and control of an account assigned that role. The issue is fixed in versions 1.8.14, 1.9.9, and 1.10.8.
PinePods versions prior to 0.9.0 contain a server-side request forgery (SSRF) vulnerability that allows authenticated low-privilege users to make the server perform HTTP GET and HEAD requests to arbitrary internal and external URLs. This occurs because the application does not validate or restrict URLs in podcast RSS feed enclosures, enabling attackers to access internal services, including cloud metadata endpoints. The vulnerability is fixed in version 0.9.0.
MyTube is a self-hosted downloader and player for several video websites. Prior to version 1.10.3, `server.ts` calls `registerStaticRoutes` and `registerCloudRoutes` before `registerApiRoutes`, where `authMiddleware` and `roleBasedAuthMiddleware` are mounted. Because Express processes middleware in registration order, `staticRoutes.ts` and `cloudRoutes.ts` remain outside the authentication stack even when `loginEnabled=true`. Unauthenticated clients can access local videos through `/videos/*`, thumbnails through `/images/*` and `/images-small/*`, avatars through `/avatars/*`, subtitles through `/subtitles/*`, cloud thumbnail caches through `/api/cloud/thumbnail-cache/*`, and cloud signed URLs or redirects through `/cloud/videos/:filename` and `/cloud/images/:filename`. The frontend login wall does not protect direct media requests. Cloud routes return 404 when cloud storage is unconfigured, but that is not an authentication rejection; protected API routes correctly return 401. Combined with hidden-video path leaks, the flaw permits unauthenticated downloads of hidden media. Default loginEnabled=false single-user deployments have no authentication boundary to bypass. This issue is fixed in version 1.10.3.
CVE-2026-62301 is a missing authorization vulnerability in franklioxygen MyTube versions prior to 1.10.3. When login is enabled with a visitor password configured, the backend does not enforce the intended public-only restriction for visitor roles. This allows unauthenticated visitors to enumerate and access hidden videos and media files that should be restricted. The issue is fixed in version 1.10.3.
CVE-2026-55493 is an authorization vulnerability in HotCRP conference review software versions 2.101 up to but not including 3.3. The flaw allows an authenticated user with search access to infer the identity of authors of anonymous comments by exploiting the 'cmt:USER' search term, which fails to properly check whether the commenter's identity should be visible. This compromises reviewer anonymity. The issue is fixed in version 3.3.
Multiple critical security vulnerabilities have been identified in the python-pillow library used in Red Hat Enterprise Linux 8. These include heap buffer overflows in TIFF saving and FlashPix JPEG decoding, as well as an argument injection vulnerability in Ghostscript calls that could lead to remote code execution. Red Hat has issued a security advisory with updates to address these issues.
OSAC operator is a Kubernetes operator. In the affected revision identified as 8220502, the `console-proxy` `RemoteConfigResolver` parses Kubernetes Secret kubeconfig data with `clientcmd.RESTConfigFromKubeConfig` without sanitizing the resulting `rest.Config`. An attacker who can create or modify a Secret labeled `osac.openshift.io/remote-cluster-kubeconfig`: "true" in a namespace where the proxy's RoleBinding grants Secret read access can supply `users[].user.exec`. When `rest.TransportFor` builds the HTTP transport for an upstream WebSocket connection, client-go invokes that exec credential plugin, spawning an arbitrary process as the osac-`console-proxy` service account inside the pod. Attacker-controlled `clusters[].server` also enables server-side request forgery from the proxy pod. Remote and auto VM cluster modes are affected, with auto the default; exclusively `local` mode does not read kubeconfig Secrets and is unaffected. The credential-plugin execution path is patched in commit 7e4222b; that patch does not address the described server-address SSRF path.
CVE-2026-119730 is an address bar spoofing vulnerability in Maxthon Browser for Android versions before 7.5.8.103. It allows remote attackers to misrepresent a page's origin by exploiting the absence of a persistent fullscreen notification or trusted origin indicator when the Fullscreen API is used. This can trick users into believing they are on a trusted domain while interacting with attacker-controlled content, potentially leading to credential disclosure via phishing.
CVE-2026-78403 is a critical stack-based buffer overflow and missing authorization vulnerability in Thalesgroup Sentinel Keys Server on Windows. The vulnerability arises because the server does not validate the length of the first field in an HTTP request. An attacker can exploit this flaw by sending a crafted HTTP request, potentially leading to remote code execution with NT AUTHORITY\SYSTEM privileges. This affects Sentinel Keys Server versions prior to 1.3.8.0.
CVE-2026-78402 is a stack-based buffer overflow vulnerability in Thalesgroup Sentinel Keys Server on Windows. The vulnerability arises because the software does not properly validate the length of the first field in an input message. A local attacker can exploit this flaw by crafting a malicious input to trigger a buffer overflow, potentially leading to arbitrary code execution with NT AUTHORITY\SYSTEM privileges, enabling local privilege escalation. This affects versions prior to 1.3.8.0. The issue has been fixed in version 1.3.8.0.
WIT SynApps Runtime through 1.4.11 contains a browser-mediated cross-origin request forgery vulnerability that allows attackers to supply an arbitrary target address during controller onboarding, causing the victim's browser to issue discovery requests to attacker-specified hosts at paths such as /easy/GUI/Skins/Default/SiteLogo and /easy/GUI/Skins/Default/Identity. Attackers can leverage the victim's browser reachability to probe loopback addresses, local hostnames, or internal-only network hosts and initiate the enrollment flow against REDY instances, crossing IT/OT segmentation boundaries through a sanctioned application path.
praktor is a multi-agent Claude Code orchestrator with Telegram input and output, Docker isolation, and a Mission Control UI. Prior to 0.9.1, both Telegram upload sites in `internal/telegram/bot.go` concatenate the attacker-controlled document filename into a destination path without sanitization, and `path.Join` collapses parent-directory traversal. A remote Telegram user who can message the bot can therefore write outside `uploads/` within the persistent agent workspace mounted at `/workspace/agent`. Because `allow_from: []` permits all senders by default, no prior authentication or privilege is required in that configuration. The attacker can plant or overwrite `CLAUDE.md`, instruction, skill, hook, or configuration files that the Claude agent reads and operates on across later runs, turning a document upload into stored instruction injection. The demonstrated arbitrary-write scope is the persistent agent workspace volume, not an unrestricted host-filesystem write. This issue is fixed in version 0.9.1.
WIT SynApps Runtime through 1.4.11 contains a pre-authentication reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject and execute arbitrary JavaScript by submitting a crafted LINK query parameter to the /System/Session-1 endpoint. Attackers can exploit this flaw to harvest credentials, manipulate the login flow, access browser-visible data, and perform same-origin requests to controller endpoints, including an origin-switch primitive against the internal controller in Cloud RIA scenarios.
Copernik XML Factory versions prior to 0.1.2 have an XML External Entity (XXE) vulnerability due to improper restriction of XML External Entity references when XInclude is enabled. This allows an attacker to cause the application to resolve attacker-controlled xi:include references, potentially disclosing local files or making server-side requests to internal network endpoints. The vulnerability requires specific conditions including use of the stock JDK provider without Apache Xerces, explicit enabling of XInclude, and parsing XML from untrusted sources. The issue is fixed in version 0.1.2.