OpenaevApplication · Filigran

CVE-2026-24467

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-20
Fix available
A fix is available. Upgrade to 2.0.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
OpenAEV is an open source platform allowing organizations to plan, schedule and conduct cyber adversary simulation campaign and tests. Starting in version 1.0.0 and prior to version 2.0.13, OpenAEV's password reset implementation contains multiple security weaknesses that together allow reliable account takeover. The primary issue is that password reset tokens do not expire. Once a token is generated, it remains valid indefinitely, even if significant time has passed or if newer tokens are issued for the same account. This allows an attacker to accumulate valid password reset tokens over time and reuse them at any point in the future to reset a victim’s password. A secondary weakness is that password reset tokens are only 8 digits long. While an 8-digit numeric token provides 100,000,000 possible combinations (which is secure enough), the ability to generate large numbers of valid tokens drastically reduces the required number of attempts to guess a valid password reset token. For example, if an attacker generates 2,000 valid tokens, the brute-force effort is reduced to approximately 50,000 attempts, which is a trivially achievable number of requests for an automated attack. (100 requests per second can mathematically find a valid password reset token in 500 seconds.) By combining these flaws, an attacker can mass-generate valid password reset tokens and then brute-force them efficiently until a match is found, allowing the attacker to reset the victim’s password to a value of their choosing. The original password is not required, and the attack can be performed entirely without authentication. This vulnerability enables full account takeover that leads to platform compromise. An unauthenticated remote attacker can reset the password of any registered user account and gain complete access without authentication. Because user email addresses are exposed to other users by design, a single guessed or observed email address is sufficient to compromise even administrator accounts with non-guessable email addresses. This design flaw results in a reliable and scalable account takeover vulnerability that affects any registered user account in the system. Note: The vulnerability does not require OpenAEV to have the email service configured. The exploit does not depend on the target email address to be a real email address. It just needs to be registered to OpenAEV. Successful exploitation allows an unauthenticated remote attacker to access sensitive data (such as the Findings section of a simulation), modify payloads executed by deployed agents to compromise all hosts where agents are installed (therefore the Scope is changed). Users should upgrade to version 2.0.13 to receive a fix.

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 confidence

OpenAEV versions 1.0.0 through 2.0.13 have critical flaws in the password reset mechanism: tokens never expire (remaining valid indefinitely) and are only 8 numeric digits. An unauthenticated attacker can generate multiple valid tokens for a target account, then brute-force the limited token space to find a valid one and reset the password. Since user emails are exposed by design, any account (including admins) can be targeted without knowing a real email address.

MitigationUpgrade to OpenAEV version 2.0.13 which contains the fix. Consider implementing additional controls like rate limiting on token generation and enforcing token expiration as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenaevApplication
Affected:>= 1.0.0, < 2.0.13

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenAEV version
    Check the version of Filigran Openaev currently deployed in your environment. This is typically found in the application metadata, package.json, or the running container/image tag.
    Affected if The installed version is greater than or equal to 1.0.0 and less than 2.0.13
  2. Verify password reset functionality is enabled
    Confirm that the password reset feature is enabled and accessible in your OpenAEV deployment. Check if the /password-reset or similar endpoint is publicly reachable.
    Affected if Password reset is enabled and exposed without additional authentication controls
  3. Inspect token expiration configuration
    Examine the configuration files or database settings related to password reset tokens. Look for any token expiration or timeout settings.
    Affected if Password reset tokens are configured with no expiration (remain valid indefinitely) or expiration settings are missing entirely
  4. Check token generation implementation
    Review the token generation code or configuration to determine the token format being used for password resets.
    Affected if Tokens are generated as 8-digit numeric values (limited entropy making brute-force feasible)
  5. Assess rate limiting on token generation
    Check if there are rate limiting controls, request throttling, or CAPTCHA mechanisms applied to the password reset token generation endpoint.
    Affected if No rate limiting or brute-force protections exist on the password reset request endpoint

You are affected if your OpenAEV version is between 1.0.0 and 2.0.13 and the password reset feature is enabled without proper token expiration, strong token generation, and rate limiting in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0.13 or later
Fixed in 2.0.13
Vendor patch github.com →
Interim mitigation

Upgrade to OpenAEV version 2.0.13 which contains the fix. Consider implementing additional controls like rate limiting on token generation and enforcing token expiration as defense-in-depth.

Recommended fix High confidence

2.0.13

  1. Backup the current OpenAEV installation and database before proceeding with any changes
  2. Confirm the currently installed version is >= 1.0.0 and < 2.0.13 using the system's version check command or configuration
  3. Upgrade OpenAEV to version 2.0.13 following the standard upgrade procedure for the installation method in use (e.g., package manager, Docker, or manual deployment)
  4. After upgrade, verify the password reset token mechanism now includes proper expiration by testing a password reset flow and confirming tokens become invalid after a reasonable timeframe
  5. Confirm the upgrade was successful by checking the installed version matches 2.0.13 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openaev Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24467 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24467 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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