Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7
Tag: self-hosted (12 articles)Clear

Critical GitLab flaw lets one request read any file from self-hosted servers

CISA warned that attackers are exploiting a critical flaw in self-managed GitLab servers, adding it to its exploited-vulnerabilities catalog with a forensic-triage requirement. Tracked as CVE-2026-85706 and scored 10.0, it is a path-traversal bug in GitLab's repository commits API caused by improper path confinement and missing authentication, letting an unauthenticated attacker read any file on the server with a single crafted request. Exposed files can include SSH keys, database credentials, deploy tokens, CI/CD variables, and source code. GitLab patched it on September 10, and researchers observed in-the-wild probing within about a day. GitLab.com is unaffected; the risk is concentrated on the many self-managed instances organizations run.

Check
Upgrade self-managed GitLab to 19.1.8, 19.2.6, 19.3.2, or later immediately, then rotate secrets the server could expose, including access tokens, deploy tokens, CI/CD variables, SSH keys, and cloud credentials.
Affected
Organizations running self-managed GitLab CE or EE from 18.7 up to the patched releases (CVE-2026-85706); an unauthenticated attacker can read arbitrary files, including secrets and source, in one request.
Fix
Patch now, rotate all potentially exposed secrets, review commits-API and web-server logs for unauthenticated requests with traversal patterns and unusual file access, and treat exposed unpatched instances as possibly already breached.

Critical Alby Hub flaw lets attackers drain internet-exposed Bitcoin wallets

Alby warned of a critical flaw in older versions of Alby Hub, a self-hosted Bitcoin Lightning wallet that people run on their own computer or server to hold their funds. An attacker who could reach the wallet's management interface over the internet could gain access without permission and send the owner's funds. The flaw affects versions 1.7.0 through 1.18.5, released before August 2025, and was fixed in 1.19.0 and later, with 1.24.0 the current release. Alby says one user has been affected so far and is withholding technical details for now. The core lesson is to never expose a self-hosted wallet's control interface to the public internet.

Check
If you run Alby Hub, remove any public internet access to its management interface first, then update to the current release, and check exposed instances for unauthorized access or unexpected outgoing payments.
Affected
Owners of self-hosted Alby Hub Lightning wallets on versions 1.7.0 through 1.18.5 reachable from the internet; an attacker reaching the management interface could take control of the wallet and send bitcoin.
Fix
Update Alby Hub to the current version, keep the wallet's management interface off the public internet behind a VPN or local network, use strong unique credentials, and monitor for unexpected transactions.

CISA flags exploited ownCloud flaw that lets attackers read and delete files

CISA added a critical ownCloud flaw to its exploited-vulnerabilities catalog after attackers used it to steal data from a research organization. Tracked as CVE-2023-49105 and scored 9.8, the WebDAV authentication-bypass bug lets an unauthenticated attacker who knows a victim's username read, modify, or delete that user's files when no signing key is configured, which is the platform's default. Disclosed back in November 2023, it affects ownCloud Server core versions 10.6.0 through 10.13.0 and was fixed in 10.13.1, yet unpatched instances remain exposed nearly two years later. Public exploit code exists, and CISA set a short deadline for federal agencies, underscoring that long-standing self-hosted flaws keep getting weaponized.

Check
Upgrade ownCloud Server to 10.13.1 or later now, or configure a signing key as a mitigation, and review WebDAV access logs for unusual file reads, changes, or deletions.
Affected
Organizations running ownCloud Server 10.6.0 through 10.13.0 without a signing key, the default (CVE-2023-49105); an unauthenticated attacker knowing a username can read, alter, or delete that user's files, and exploitation is active.
Fix
Patch to 10.13.1, set a signing key, restrict and monitor exposed WebDAV services, investigate for unauthorized file access or deletion, and treat any long-unpatched ownCloud instance as a likely target.

Critical Keycloak flaw lets attackers take over any account via password reset

A critical flaw in Keycloak, the widely used open-source identity and access management server, lets an unauthenticated attacker take over any account through its password-reset flow. Tracked as CVE-2026-18963, the bug is improper state validation in the reset-credentials flow: a crafted request to the reset endpoint pushes the authentication session straight to the password-update step, so the action token Keycloak normally emails is never required, and the attacker sets new credentials for a chosen user. It needs no user interaction and works against any account, including administrators. Red Hat fixed it in Keycloak 26.7.2 and related releases; there is no confirmed exploitation yet.

Check
Upgrade Keycloak to a fixed release such as 26.7.2, and if you ran a vulnerable version, revoke active and offline sessions and rotate client secrets, since tokens may already have been issued.
Affected
Organizations running Keycloak with the forgotten-password feature enabled on a vulnerable version (CVE-2026-18963); an unauthenticated attacker can reset and take over any user or admin account without the email verification step.
Fix
Patch promptly, then treat exposure as possible account compromise: revoke sessions, rotate accessible client secrets, review identity links and admin permissions, and remember downstream services may hold tokens issued before patching.

Unpatched GeoServer zero-day allowing code execution is already being probed

A newly disclosed zero-day in GeoServer, the widely used open-source geospatial server, is already drawing exploitation attempts, according to watchTowr. The flaw is a SQL injection issue that can lead to remote code execution, and it remains unpatched, with no CVE assigned yet. It was first disclosed publicly by a researcher on August 12, and attackers commonly begin probing internet-facing servers as soon as such details appear. GeoServer instances are frequently exposed to the internet to serve mapping and location data, which makes an unpatched code-execution flaw in the platform an attractive and reachable target. Defenders should treat exposed instances as at risk until a fix ships.

Check
Identify internet-facing GeoServer instances, restrict access to them, and monitor closely for exploitation, since the flaw is unpatched and attackers are already probing for vulnerable servers.
Affected
Organizations running internet-exposed GeoServer; an unpatched SQL injection flaw can lead to remote code execution, there is no fix or CVE yet, and probing for vulnerable instances has already started.
Fix
Limit GeoServer exposure behind authentication or a firewall until a patch is available, monitor for suspicious database queries and process execution, and apply the vendor fix as soon as it is released.

Leaked n8n API tokens in public code exposed live automation instances

GitGuardian found 321 live n8n automation instances reachable using API tokens that developers had accidentally committed to public GitHub repositories, and showed four ways an attacker could abuse them. n8n workflows often hold credentials for the services they connect, so a valid API token can expose not just the automation platform but the downstream accounts it touches, from cloud services to messaging and databases. Because n8n is widely self-hosted and frequently wired into sensitive systems, an exposed token can become a path to broader compromise. The finding is a reminder that secrets committed to source control remain one of the most reliable ways in.

Check
Scan your repositories and history for committed n8n API tokens and other secrets, rotate anything exposed, and confirm n8n instances are not reachable from the internet without protection.
Affected
Teams self-hosting n8n whose API tokens reached public code; an attacker can drive the automation platform and reach the downstream credentials stored in its workflows, from cloud services to databases.
Fix
Rotate exposed tokens, add automated secret scanning to block commits, scope n8n credentials tightly, keep instances behind authentication and off the public internet, and audit workflows for stored downstream credentials.

Attacker wires DeepSeek into an agent to hunt and exploit exposed servers

Palo Alto Networks Unit 42 detailed a Chinese-speaking attacker who used the DeepSeek model as the reasoning engine inside an open-source agent called Hermes to attack exposed servers with little human input. Taking instructions over Telegram and using an internet asset search engine, the agent ran in a mode that executes commands without asking permission: from a single task, it downloaded a public exploit, enumerated vulnerable Langflow and n8n instances, judged targets by value, and attempted exploitation on its own. The autonomous attempts failed, blocked by authentication and configuration, though the operator succeeded manually elsewhere. The operation was exposed when the agent accidentally served its own working directory over the web.

Check
Keep self-hosted tools like n8n and Langflow patched, authenticated, and off the public internet, since autonomous agents now scan asset search engines and attempt exploitation without a human in the loop.
Affected
Organizations exposing self-hosted AI and automation tools such as Langflow and n8n; autonomous AI agents can discover, rank, and attack them at scale, though basic authentication and hardening blocked the observed attempts.
Fix
Require authentication, disable risky auto-login options, restrict management interfaces, and patch known flaws, since the defensive configurations that stopped this agent are the same controls that blunt automated exploitation generally.

n8n sandbox escape lets workflow editors run commands on the server

n8n patched a high-severity flaw that lets an authenticated user who can create or edit workflows escape the expression sandbox and run operating-system commands as the n8n process. Security Joes found it while probing n8n's February fix for an earlier sandbox bug, and the gap sits in how the rewriter handled a bare identifier in a concise arrow function body. Successful exploitation can expose the n8n encryption key and allow decryption of stored credentials. It is tracked as GHSA-gv7g-jm28-cr3m with a score of 8.7 and no CVE assigned yet. Fixed versions are 2.31.5 and 2.32.1, with no patched 1.x release listed.

Check
Update self-hosted n8n to 2.31.5 or 2.32.1 or later, and treat the vendor's interim advice to restrict editing to trusted users as an incomplete stopgap rather than a fix.
Affected
Self-hosted n8n deployments before 2.31.5 or on 2.32.0 (GHSA-gv7g-jm28-cr3m); any account allowed to create or modify workflows can run commands as the n8n process and expose stored credentials.
Fix
Upgrade to a fixed release, rotate the n8n encryption key and stored credentials if you ran an exposed version, and keep the instance off the public internet.

Attackers exploit Windmill flaw to read server files and reach superadmin access

VulnCheck reports active exploitation of a path traversal flaw in Windmill, an open source platform for building internal tools, jobs, and workflows. CVE-2026-29059 lets an unauthenticated attacker read arbitrary files through the log file endpoint, and while observed attempts included reading the password file, the higher value target is the superadmin secret. Where that is configured, an attacker can authenticate as a super administrator and run arbitrary code through the job preview API. VulnCheck counted roughly 170 exposed instances across 24 countries, including deployments reachable through a proxy path rather than directly.

Check
Update Windmill to a fixed release, confirm whether any instance was reachable from the internet, and treat the superadmin secret and any credentials stored in configuration as exposed.
Affected
Organizations running internet-reachable Windmill deployments (CVE-2026-29059); unauthenticated attackers read server files, and where the superadmin secret is set, escalate to full administrative access and code execution.
Fix
Patch to the fixed version, rotate the superadmin secret and stored credentials, keep internal automation platforms off the public internet or behind authentication, and review logs for file read attempts.

n8n token exchange flaw could let attackers log in as other users

A vulnerability in the workflow automation platform n8n could let an attacker log in as another user without their password. Tracked as CVE-2026-59208, the flaw sits in n8n's Enterprise token exchange feature, which lets embedded deployments avoid a second login by accepting tokens from partner identity providers. Because the code did not properly bind an identity to its issuer, a valid token from one issuer that carried the identifier of a user under a different issuer would log the attacker in as that user. n8n shipped a fix on June 24, and there is no evidence of exploitation. The bug was found by an AI penetration-testing agent.

Check
Check whether you run n8n, especially Enterprise deployments using the token exchange feature for embedding or single sign-on, confirm the version, and update to a release that includes the June fix.
Affected
Organizations running n8n Enterprise deployments that use the token exchange feature (CVE-2026-59208); a flaw in binding identities to issuers could let an attacker present a token and log in as another user.
Fix
Update n8n to a version containing the June 24 fix, review authentication logs for unexpected cross-issuer logins, and apply least privilege so that a single compromised account has limited reach.