CVE-2025-7777
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe mirror-registry doesn't properly sanitize the host header HTTP header in HTTP request received, allowing an attacker to perform malicious redirects to attacker-controlled domains or phishing campaigns.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencemirror-registry is vulnerable to HTTP Host Header Injection because it uses the Host header from incoming HTTP requests without validation or sanitization when performing redirects. An attacker can manipulate the Host header to redirect users to malicious attacker-controlled domains, facilitating phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify mirror-registry installation and versionRun 'mirror-registry --version' or check the installed package version via your system's package manager (e.g., 'rpm -q mirror-registry' or 'dpkg -l mirror-registry')Affected if The installed version matches the affected version range for CVE-2025-7777 and redirect functionality is in use
-
Verify HTTP redirect functionality is enabledReview the mirror-registry configuration files (typically in /etc/mirror-registry/ or ~/.mirror-registry/) and look for redirect-related settings, or examine the application logs for 3xx redirect responsesAffected if HTTP redirects are enabled and the application processes incoming HTTP requests containing a Host header
-
Inspect redirect handling code or configurationIf source code is available, search for code that processes the Host header and constructs redirect responses (look for 'Redirect', 'Location', 'http.Redirect', or similar). If only configuration is accessible, check for any Host validation settingsAffected if The application uses the incoming Host header value directly in Location headers without validation or sanitization
-
Test for Host header injection via HTTP requestSend a request to the mirror-registry endpoint with a manipulated Host header (e.g., 'Host: attacker-controlled-domain.com') and observe if the response includes a redirect to the attacker-specified domainAffected if The application returns a 3xx redirect with a Location header matching the value from the attacker-controlled Host header
Your environment is affected if mirror-registry is running and performs redirects using the unsanitized Host header from incoming requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based validation of the Host header, rejecting requests with unexpected host values and using a fixed list of permitted redirect destinations.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7777 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data