dbcve.org
AffineApplication

CVE-2026-25477

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-02
Fix available
A fix is available. Upgrade to 0.26.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
AFFiNE is an open-source, all-in-one workspace and an operating system. Prior to version 0.26.0, there is an Open Redirect vulnerability located at the /redirect-proxy endpoint. The flaw exists in the domain validation logic, where an improperly anchored Regular Expression allows an attacker to bypass the whitelist by using malicious domains that end with a trusted string. This issue has been patched in version 0.26.0.

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

Open Redirect vulnerability in AFFiNE's /redirect-proxy endpoint. The domain validation uses an improperly anchored Regular Expression (likely missing start ^ and/or end $ anchors), allowing bypass of the whitelist by using malicious domains that end with a trusted string (e.g., 'evil.comtrusted.com' matching 'trusted.com').

MitigationUpgrade AFFiNE to version 0.26.0 or later, which contains the patch for the improperly anchored regex in the domain validation logic.

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
AffineApplication
Affected:< 0.26.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checks

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

  1. Identify AFFiNE installation method
    Determine how AFFiNE is deployed: check for Docker containers, npm packages, or direct binary installation. Look for container names, process listings, or package.json files that reference 'affine' or 'toeverything'.
    Affected if AFFiNE is installed via any method and the version is below 0.26.0
  2. Determine installed AFFiNE version
    Run the version check command appropriate to your installation method: for Docker, run 'docker ps' and inspect labels or check the container's reported version; for npm installations, run 'npm list @toeverything/infra' or check package.json; for binary installations, run the binary with '--version' or check the about page in the web interface.
    Affected if The version returned is less than 0.26.0 (e.g., 0.25.x, 0.24.x, etc.)
  3. Verify /redirect-proxy endpoint accessibility
    Check if your AFFiNE instance exposes the /redirect-proxy endpoint by accessing it directly or reviewing your reverse proxy/web server configuration for routes forwarding to this path. Attempt a curl request to yourdomain/redirect-proxy to confirm the endpoint responds.
    Affected if The /redirect-proxy endpoint is accessible and returns a response (rather than a 404)
  4. Test for unanchored regex bypass
    Send a request to /redirect-proxy?url=http://evil.comtrusted.com (where 'trusted.com' is your own legitimate domain you control) and observe if the server accepts this and attempts to redirect. Compare the behavior against a request using just your trusted domain alone.
    Affected if The server accepts the bypass URL and will redirect to the attacker-controlled domain embedded in the URL (the validation logic matches 'trusted.com' at the end of 'evil.comtrusted.com')

A user is affected if their AFFiNE instance is version 0.26.0 or earlier AND the /redirect-proxy endpoint is accessible and accepts the regex bypass test.

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 0.26.0 or later
Fixed in 0.26.0
Interim mitigation

Upgrade AFFiNE to version 0.26.0 or later, which contains the patch for the improperly anchored regex in the domain validation logic.

Recommended fix High confidence

0.26.0

  1. Upgrade AFFiNE to version 0.26.0 or later by following the official upgrade documentation for your deployment method
  2. Verify the upgrade was successful by checking the AFFiNE version in the system settings or via CLI
  3. Confirm the /redirect-proxy endpoint now properly validates domains using a correctly anchored Regular Expression - the vulnerability is patched in version 0.26.0

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

Fix this in Affine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-25477 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