vciy

CVE-2026-44427

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

MCP Registry: Open Redirect

CVE-2026-444273 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposureunder $1over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

under $1 = $4.99M incident cost x 0 exposure x 0.0041 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.0041EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-05-15, 70 days at 0.00, as of 2026-07-24. arc-rules@v1

Foresight · where to check next

Google ChromeCVE-2012-051844427

This record is one instance of CWE-601, url redirection to untrusted site ('open redirect'). The index holds 1738 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signal

Running modelcontextprotocol registry? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · passive user interaction · low attack complexity · no attack requirementsreceipt
ImpactNo confidentiality, integrity or availability impactreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-601 URL Redirection to Untrusted Site ('Open Redirect')receipt
Published consequencesCWE-601: Access Control: Bypass Protection Mechanism, Gain Privileges or Assume Identity; Access Control, Confidentiality, Other: Bypass Protection Mechanism, Gain Privileges or Assume Identity, Other[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 24 Jul 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.0041 · top 65% of all CVEsreceipt
Assigned byGitHub_Mreceipt
Recorded changes5 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productmodelcontextprotocol registryreceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. From 1.1.0 to 1.7.4, the TrailingSlashMiddleware in internal/api/server.go is vulnerable to an open redirect attack. An attacker can craft a URL with a protocol-relative path (e.g., //evil.com/) that, after trailing slash removal, results in a Location header of //evil.com — which browsers interpret as an absolute URL to an external domain. This vulnerability is fixed in 1.7.5. receipt

NVD's analysis a second authority

weakness
CWE-601
also scored by
[email protected] 0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

check it yourself github.com receipt

Movement the material steps

15 May 20260.00041
15 Jun 20260.00409 · scoring model v2026.06.15
24 Jul 20260.0041
Show all 5 observations
15 May 20260.00041
20 May 20260.00054
22 May 20260.00017
15 Jun 20260.00409
24 Jul 20260.0041

5 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.0041Published2026-05-14Index as of2026-07-24

The record had been public for 2 months when this index was last written.

Published 2026-05-14 receipt · Index as of 2026-07-24 derived

The pattern, elsewhere

This record is one instance of CWE-601, url redirection to untrusted site ('open redirect'). The index holds 1738 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2021-38000 · Google Chromeonly 1 attribute comparableKEV listed · 2021receipt
CVE-2012-0518nothing comparable heldKEV listed · 2012receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

1738 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2026-44427.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.