thinQtankLABS

Web Server Patch Triage & Remediation: CVE-2026-42945

Triage a High-severity NGINX heap-overflow finding (CVE-2026-42945) on an internet-facing reverse proxy: confirm the version, score it with CVSS and see why AC:H keeps it below Critical, judge exposure, upgrade to the fixed release and verify.

Beginner 20 guided steps 5 tasks About 50 minutes Runs in your browser

Skills you will practice

  • Web server vulnerability management
  • Version confirmation
  • CVSS v3.1 scoring (attack complexity)
  • Internet-facing exposure assessment
  • Patch verification

The scenario

You are the web analyst on call. The scanner flagged CVE-2026-42945 — an unauthenticated heap overflow in NGINX's rewrite module — on an internet-facing reverse proxy. Start by understanding it.

What you will do

  1. Triage the alert4 steps

    Open the ticket · Read the scan report · Which CVE? · Read the ticket

  2. Confirm the version5 steps

    Check the NGINX version · What version is running? · Read the advisory · Is the host affected? · …

  3. Assess the severity4 steps

    Find the CVSS vector · Compute the base score · What is the base score? · Why not Critical?

  4. Confirm exposure and scan2 steps

    Check exposure · Baseline scan

  5. Remediate and verify5 steps

    Which fixed version? · Upgrade NGINX · Confirm the version · Verify with a scan · …

How this lab works

A real Linux-style console. Commands run against real files, so hashes, hex dumps and comparisons give real results.

A file browser where you can place evidence into the lab, either the file provided or one of your own.

Reset a single step, a whole task or the entire lab. The environment is rebuilt so you can try again cleanly.

Progress saves after every step. Close the tab and come back later; your files and answers are waiting.