CVE-2026-52909
In the Linux kernel, the following vulnerability has been resolved: ip6_vti: set netns_immutable on the fallback device. john1988 and Noam
CVSS
7.8
High
EPSS
0.1%
p1
KEV
—
Exploit Today
0
0-100
Published: Jun 19, 2026 · Last modified: Oct 19, 2026 · CWE-863
0.1%EPSS · 30 days0.1%
2026-10-042026-11-01
In the Linux kernel, the following vulnerability has been resolved: ip6_vti: set netns_immutable on the fallback device. john1988 and Noam Rathaus reported that vti6_init_net() does not set the netns_immutable flag on the per-netns fallback tunnel device (ip6_vti0). Other similar tunnel drivers (like ip6_tunnel, sit, ip6_gre, and ip_tunnel) correctly set this flag during their fallback device initialization to prevent them from being moved to another network namespace.
- git.kernel.orghttps://git.kernel.org/stable/c/12acc977838c943636fb01e2f3087d2e4cc3b7cc
- git.kernel.orghttps://git.kernel.org/stable/c/12c65e2c7fef507551bd7b52123598a761662c01
- git.kernel.orghttps://git.kernel.org/stable/c/7f28e3948c59481f8db9c9638e204258d26b4e41
- git.kernel.orghttps://git.kernel.org/stable/c/c5dbd669db5a426b3025512322e1bf2cdbe14305
- git.kernel.orghttps://git.kernel.org/stable/c/d289d5307762d1838aaece22c6b6fcad9e8865f9
- git.kernel.orghttps://git.kernel.org/stable/c/dcdce3bc9f08026ff3739ee7339e1bef526fc5f3
- git.kernel.orghttps://git.kernel.org/stable/c/ecf8904067dcba0dad86ece80874841e60317885
- git.kernel.orghttps://git.kernel.org/stable/c/f4b6b4af7ef0661ac153c6f7eb1030aa8482c1a3
- cert-portal.siemens.comhttps://cert-portal.siemens.com/productcert/html/ssa-784472.html
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1204894.3 MED—
———Outline before 1.12.0 contains an incorrect authorization vulnerability in authorizeDocumentPublish() that allows authenticated members to publish documents into private collections without write access. Attackers can detach a child document via documents.unpublish, retaining parentDocumentId, then call documents.update with a private collection UUID to inject phishing content.6hCVE-2026-1204877.2 HIG—
———LaraDashboard before 1.4.5 contains an incorrect authorization vulnerability in SettingPolicy::manageCoreUpgrades() that allows non-Superadmin administrators with settings.edit to access Superadmin-only core-upgrade operations. Attackers can use the /admin/settings/core-upgrades backup, download, restore and upgrade actions to obtain database dumps containing password hashes and restore or upgrade the site.6hCVE-2026-1204504.3 MED—
———LaraDashboard 1.4.0 before 1.4.9 contains an improper authorization vulnerability that allows authenticated users with read-only email_template.view permission to send arbitrary emails via the MCP send-email tool. Attackers can mint an MCP token and call send-email with any recipient, subject, and raw HTML body to deliver phishing or spam from the site's mailer.6hCVE-2026-1204458.8 HIG—
———madong-admin-saas through 5.1.4 contains an incorrect authorization vulnerability in AccessTokenMiddleware that allows authenticated tenant users to access the platform management API in multi-tenant mode. Attackers can reuse a tenant login JWT against /platformapi controllers to create platform administrator accounts, read tenant database settings, and take control of every tenant.5hCVE-2026-119625—17.0%
——5The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`.1dCVE-2026-119441—9.6%
——3`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens.1d