GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-r3j6-gpjw-qfjrmedium6.5

Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used

Check your stack

The advisory, in context

A flaw in the handling of one-time codes for app-based multi-factor authentication allows a previously issued code to be used after a newer code has already been accepted. This issue does not affect email-based MFA. Submitting the exact same code twice was already prevented, but any other code within the accepted time window was not.

If an attacker gains access to both the user's password and a single one-time code, that code stays usable for the remainder of its time window, which is around four minutes on the default settings, including after the legitimate user has already logged in with a newer code.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 4.0.0 before 4.12.6

Fixed in 4.12.6

87 explicitly affected versions

v4.0.0, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.13, v4.0.14, v4.0.15, v4.0.16, v4.0.17, v4.0.18, v4.0.19, v4.0.2, v4.0.20, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1, v4.1.10, v4.1.2, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.10.0, v4.10.1, v4.10.2, v4.11.0, v4.11.1, v4.11.2, v4.11.3, v4.11.4, v4.11.5, v4.11.6, v4.11.7, v4.11.8, v4.12.0, v4.12.0-beta1, v4.12.0-beta2, v4.12.0-beta3, v4.12.0-beta4, v4.12.1, v4.12.2, v4.12.3, v4.12.4, v4.12.5, v4.2.0, v4.2.1, v4.2.2, v4.2.3, v4.2.4, v4.3.0, v4.3.1, v4.4.0, v4.5.0, v4.5.1, v4.5.2, v4.5.3, v4.6.0, v4.6.1, v4.6.2, v4.6.3, v4.7.0, v4.7.1, v4.7.2, v4.7.3, v4.7.4, v4.8.0, v4.8.1, v4.8.2, v4.8.3, v4.8.4, v4.8.5, v4.9.0, v4.9.1, v4.9.2, v4.9.3, v4.9.4, v4.9.5

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "4.0.0"
        },
        {
          "fixed": "4.12.6"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v4.0.0",
    "v4.0.1",
    "v4.0.10",
    "v4.0.11",
    "v4.0.12",
    "v4.0.13",
    "v4.0.14",
    "v4.0.15",
    "v4.0.16",
    "v4.0.17",
    "v4.0.18",
    "v4.0.19",
    "v4.0.2",
    "v4.0.20",
    "v4.0.3",
    "v4.0.4",
    "v4.0.5",
    "v4.0.6",
    "v4.0.7",
    "v4.0.8",
    "v4.0.9",
    "v4.1.0",
    "v4.1.1",
    "v4.1.10",
    "v4.1.2",
    "v4.1.3",
    "v4.1.4",
    "v4.1.5",
    "v4.1.6",
    "v4.1.7",
    "v4.1.8",
    "v4.1.9",
    "v4.10.0",
    "v4.10.1",
    "v4.10.2",
    "v4.11.0",
    "v4.11.1",
    "v4.11.2",
    "v4.11.3",
    "v4.11.4",
    "v4.11.5",
    "v4.11.6",
    "v4.11.7",
    "v4.11.8",
    "v4.12.0",
    "v4.12.0-beta1",
    "v4.12.0-beta2",
    "v4.12.0-beta3",
    "v4.12.0-beta4",
    "v4.12.1",
    "v4.12.2",
    "v4.12.3",
    "v4.12.4",
    "v4.12.5",
    "v4.2.0",
    "v4.2.1",
    "v4.2.2",
    "v4.2.3",
    "v4.2.4",
    "v4.3.0",
    "v4.3.1",
    "v4.4.0",
    "v4.5.0",
    "v4.5.1",
    "v4.5.2",
    "v4.5.3",
    "v4.6.0",
    "v4.6.1",
    "v4.6.2",
    "v4.6.3",
    "v4.7.0",
    "v4.7.1",
    "v4.7.2",
    "v4.7.3",
    "v4.7.4",
    "v4.8.0",
    "v4.8.1",
    "v4.8.2",
    "v4.8.3",
    "v4.8.4",
    "v4.8.5",
    "v4.9.0",
    "v4.9.1",
    "v4.9.2",
    "v4.9.3",
    "v4.9.4",
    "v4.9.5"
  ]
}
Ecosystem versions

From 5.0.0 before 5.7.6

Fixed in 5.7.6

44 explicitly affected versions

v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.2.4, v5.3.0, v5.3.1, v5.3.2, v5.3.3, v5.3.4, v5.3.5, v5.4.0, v5.4.1, v5.4.2, v5.4.3, v5.4.4, v5.4.5, v5.5.0, v5.5.1, v5.5.2, v5.6.0, v5.6.1, v5.6.2, v5.6.3, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.7.0, v5.7.0-beta1, v5.7.0-beta2, v5.7.0-beta3, v5.7.0-beta4, v5.7.1, v5.7.2, v5.7.3, v5.7.4, v5.7.5

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "5.0.0"
        },
        {
          "fixed": "5.7.6"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v5.0.0",
    "v5.1.0",
    "v5.1.1",
    "v5.1.2",
    "v5.1.3",
    "v5.2.0",
    "v5.2.1",
    "v5.2.2",
    "v5.2.3",
    "v5.2.4",
    "v5.3.0",
    "v5.3.1",
    "v5.3.2",
    "v5.3.3",
    "v5.3.4",
    "v5.3.5",
    "v5.4.0",
    "v5.4.1",
    "v5.4.2",
    "v5.4.3",
    "v5.4.4",
    "v5.4.5",
    "v5.5.0",
    "v5.5.1",
    "v5.5.2",
    "v5.6.0",
    "v5.6.1",
    "v5.6.2",
    "v5.6.3",
    "v5.6.4",
    "v5.6.5",
    "v5.6.6",
    "v5.6.7",
    "v5.6.8",
    "v5.7.0",
    "v5.7.0-beta1",
    "v5.7.0-beta2",
    "v5.7.0-beta3",
    "v5.7.0-beta4",
    "v5.7.1",
    "v5.7.2",
    "v5.7.3",
    "v5.7.4",
    "v5.7.5"
  ]
}

References