CVE-2025-26961
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 · uneditedMissing Authorization vulnerability in FRESHFACE Fresh Framework fresh-framework allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Fresh Framework: from n/a through <= 1.70.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 · moderate confidenceMissing authorization vulnerability in Fresh Framework allows users to access functionality that should be constrained by Access Control Lists (ACLs). This is a broken access control issue where certain functions or endpoints lack proper permission checks, potentially allowing unauthorized actions.
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
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
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 Fresh Framework installation and versionRun `deno --version` to confirm Deno runtime, then check your project's deno.json or lock file for Fresh framework version, or run `deno info` on your Fresh project entry pointAffected if The installed Fresh Framework version is 1.70.0 or lower, or version cannot be determined
-
Locate custom routes and API endpointsInspect the routes/ directory in your Fresh project for .ts files defining handlers. Also check any api/ directories and any manually registered handlers in your main entry point (routes/index.tsx or main.ts)Affected if The codebase contains routes or API endpoints that do not implement explicit authorization checks (e.g., no ACL middleware, no permission validation on handlers)
-
Review handler implementations for ACL enforcementOpen each route/endpoint file identified and search for authorization logic: look for imports of ACL modules, permission checking functions, session validation, or role-based access code. Check if handlers begin with permission validation before executing sensitive operationsAffected if Any handler that performs privileged operations (database writes, user data access, admin functions) lacks ACL or permission check code at the function entry point
You are affected if your Fresh Framework installation is version 1.70.0 or lower AND your codebase contains routes or endpoints that perform sensitive operations without explicit authorization/ACL validation checks.
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 dataUpdate Fresh Framework to version >1.70.0 if a patch is available; otherwise conduct a code audit to identify and remediate all unprotected functions with proper ACL implementation.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26961 — 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-26961 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