CVE-2025-64487
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 · uneditedOutline is a service that allows for collaborative documentation. Prior to 1.1.0, a privilege escalation vulnerability exists in the Outline document management system due to inconsistent authorization checks between user and group membership management endpoints. This vulnerability is fixed in 1.1.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 confidenceOutline versions prior to 1.1.0 contain a privilege escalation vulnerability caused by inconsistent authorization checks between user and group membership management endpoints. An attacker with low-level access could exploit these mismatched authorization controls to elevate their privileges within the system, potentially gaining administrative capabilities.
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< 1.1.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Outline versionRun 'outline version' command or check the Docker image tag/label if running in a container. On self-hosted installations, check package.json or the application's /api/status endpoint for version information.Affected if Installed version is below 1.1.0 (e.g., 1.0.x, 0.x.x series)
-
Verify API endpoint accessibilityCheck if the user management API endpoints (typically /api/users and /api/groups) are accessible from the network where low-privileged users operate. Use curl or a browser to inspect HTTP response codes.Affected if Endpoints return 200 OK instead of 403 Forbidden for non-admin users
-
Confirm user and group management is enabledReview the Outline configuration file (outline.yml or environment variables) to verify that user and group management features are not explicitly disabled via settings like 'MAX_TEAM_MEMBER_COUNT' restrictions or 'authentication' configuration.Affected if User/group management is active and not restricted by configuration
-
Test authorization boundary for group membershipSubmit a crafted API request to add a user to an administrative group using a low-privilege account token. Observe if the operation succeeds when it should be denied.Affected if Low-privilege user can successfully modify group membership that should be restricted to administrators
You are affected if Outline version is below 1.1.0 and user/group management features are accessible, allowing unauthorized privilege escalation through group membership APIs.
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.
dbcve · scoped1.1.0
Upgrade Outline to version 1.1.0 or later to apply the authorization fix. Conduct post-upgrade access control testing to verify the privilege escalation vectors are properly closed.
1.1.0
- Backup your Outline instance database and configuration files before upgrading
- Review the Outline 1.1.0 release notes and migration guide for any required migration steps
- Stop the Outline service
- Upgrade Outline to version 1.1.0 using your deployment method (e.g., Docker, npm, or your package manager)
- Verify the upgrade was successful by checking the version number
- Restart the Outline service
- Test that user and group membership management functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-64487 — 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-64487 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