<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webserver on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/webserver/</link><description>Recent content in Webserver on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 13:12:48 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/webserver/index.xml" rel="self" type="application/rss+xml"/><item><title>Nginx Map Regex Flaw Lets One Request Take Over a Server</title><link>https://hackingpassion.com/nginx-map-regex-rce/</link><pubDate>Tue, 21 Jul 2026 13:12:48 +0200</pubDate><guid>https://hackingpassion.com/nginx-map-regex-rce/</guid><description>&lt;p>For 15 years, a single crafted web request could quietly take over an nginx server, the software that receives and routes incoming traffic for roughly a third of the websites people load.
The flaw was documented in public years ago and marked as something to fix, and the danger went unrecognised until a researcher looked again last week.&lt;/p>
&lt;p>nginx is the piece of software sitting in front of a large slice of the internet. When you open a site, there is a good chance nginx is the first thing that reads your request, deals with the encryption, decides where the request should go, and passes it to whatever runs the site behind it.&lt;/p></description></item></channel></rss>