view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Only if the next one targets http3 instead of http2 😉
this one is targeting http3 too
It's explicitly exploiting the http2 flow control and neither 1.1 (the link above even suggests deactivating http2 as a temporary measure) nor –afaik– http3 (which works differently just by design principle) are affected.
https://www.cve.org/CVERecord?id=CVE-2026-121810
I assumed we are talking about the title specifically.
Crashing your service with an exploit depending "on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled" that "may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution" may be a critical issues, too, but is not exactly the same thing as a proven way to get root access.
edit: this was a duplicate
this CVE is also listed on the page linked in the post. and the root privileges are gained through a linux vulnerability, the nginx cves dont give root they just allow arbitrary code execution