dbcve.org
Gt Edge AiWeb browser · Gtedge

CVE-2025-63664

HIGH · 7.5 CVSS v3.1 Published 2025-12-22
Fix available
A fix is available. Upgrade to 2.0.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Incorrect access control in the /api/v1/conversations/*/messages API of GT Edge AI Platform before v2.0.10-dev allows unauthorized attackers to access other users' message history with AI agents.

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

GT Edge AI Platform before v2.0.10-dev contains an Insecure Direct Object Reference (IDOR) vulnerability in the /api/v1/conversations/*/messages API endpoint. The endpoint fails to validate that the requesting user owns the specified conversation, allowing attackers to enumerate conversation IDs and access other users' private message histories with AI agents.

MitigationUpgrade to GT Edge AI Platform v2.0.10-dev or later which implements proper authorization checks on the conversations API endpoint to ensure users can only access their own message histories.

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
Gt Edge AiWeb browser
Affected:< 2.0.12

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 GT Edge AI Platform installation
    Locate the GT Edge AI Platform installation directory or check running services. Look for version indicators in the application UI, startup logs, or version files in the installation root.
    Affected if GT Edge AI Platform is installed and running
  2. Determine installed version
    Check the application's version number. Common locations: about page in the UI, version file in the installation directory, or API endpoint such as /api/v1/version or /health. Compare the version to the affected range of < 2.0.12.
    Affected if Version is less than 2.0.12
  3. Verify API endpoint accessibility
    Confirm the /api/v1/conversations/*/messages endpoint is exposed and accessible in the environment. Check network configuration, API gateway settings, or firewall rules.
    Affected if The endpoint is reachable from the network where attackers could send requests
  4. Test for authorization gap
    Using an authenticated user session, make a request to /api/v1/conversations/{id}/messages where {id} is a conversation ID that does not belong to the current user. If the response returns message history for the other user's conversation, the vulnerability is present.
    Affected if Requests to conversation IDs belonging to other users return data instead of returning 403 Forbidden or 404 Not Found

The environment is affected if GT Edge AI Platform version is less than 2.0.12 AND the /api/v1/conversations endpoint is accessible AND unauthorized users can access other users' conversation message histories.

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.12 or later
Fixed in 2.0.12
Interim mitigation

Upgrade to GT Edge AI Platform v2.0.10-dev or later which implements proper authorization checks on the conversations API endpoint to ensure users can only access their own message histories.

Recommended fix Moderate confidence

v2.0.10-dev or later (recommended: v2.0.12 or latest stable)

  1. 1. Identify the current installed version of GT Edge AI Platform by checking the application settings or running 'gt-edge-ai --version'
  2. 2. If the current version is before v2.0.10-dev (or v2.0.12 if following the more conservative affected versions listing), plan for an upgrade
  3. 3. Review the GT Edge AI Platform release notes for v2.0.10-dev (or v2.0.12) to understand changes and any required migration steps
  4. 4. Create a backup of the current configuration and database
  5. 5. Stop the GT Edge AI Platform service
  6. 6. Upgrade to version v2.0.10-dev or later (recommended: v2.0.12 or latest stable release)
  7. 7. Verify the upgrade was successful by checking the version
  8. 8. Restart the GT Edge AI Platform service

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

Fix this in Gt Edge Ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-63664 — 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-2025-63664 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