dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-27559

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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 default permissions for some AI Playground software before version v2.3.0 alpha may allow an authenticated user to potentially enable escalation of privilege via local access.

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 confidence

AI Playground software versions before v2.3.0 alpha contain incorrect default file or directory permissions that allow an authenticated local user to modify or access resources beyond their intended authorization level, enabling local privilege escalation.

MitigationUpgrade AI Playground to version v2.3.0 alpha or later to obtain corrected default permissions; additionally review and harden file system permissions on the host system to ensure least-privilege access controls.

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
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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. Check AI Playground installed version
    Locate the AI Playground installation directory and find the version file or executable. Common locations include /opt/ai-playground, /usr/local/ai-playground, or the application binary. Run 'ls -la' on the main directory and look for version information in a README, VERSION file, or by running 'ai-playground --version' if the binary is in PATH
    Affected if The installed version is before v2.3.0 alpha (e.g., v2.2.x, v2.1.x, or any version number lower than v2.3.0)
  2. Identify AI Playground data and configuration directories
    Find directories used by AI Playground for storing data, models, configurations, and logs. Common locations include the installation directory itself, ~/.ai-playground, /var/lib/ai-playground, or /home/*/ai-playground. Check the main executable or documentation for default paths
    Affected if The software is installed and any of these directories exist on the system
  3. Examine file permissions on installation directories
    Run 'ls -la' on the AI Playground installation directory and all subdirectories. Look for permissions that allow write access by non-owner users (permissions containing 'w' for 'others' or inappropriate 'group' members)
    Affected if Any directory or file shows permissions like 777, 775, 774, 666, or similar that grant write access to others or to a group that includes untrusted users
  4. Check for world-writable files or directories
    Run 'find /path/to/ai-playground -perm -002 -type f' to find world-writable files, and 'find /path/to/ai-playground -perm -002 -type d' for world-writable directories. Also check for setuid/setgid files with 'find /path/to/ai-playground -perm /6000'
    Affected if Any file or directory is found with world-writable permissions, especially configuration files, scripts, or executables
  5. Verify low-privileged user access to sensitive files
    Create a test with a low-privileged user account (or use an existing non-admin account). Attempt to read or modify files in the AI Playground directory that should only be accessible to the admin or root user. Use 'su -c 'cat /path/to/file' username' or login as that user and try to write to directories
    Affected if A non-privileged user can modify configuration files, scripts, model files, or other resources that should be restricted to admin or system accounts

You are affected if AI Playground version is before v2.3.0 alpha AND any file or directory in the installation has permissions allowing authenticated local users (beyond their authorized scope) to write to files or directories they should not have access to.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AI Playground to version v2.3.0 alpha or later to obtain corrected default permissions; additionally review and harden file system permissions on the host system to ensure least-privilege access controls.

Recommended fix Moderate confidence

Intel AI Playground v2.3.0 alpha or later

  1. Identify the current installed version of Intel AI Playground software
  2. Locate and download Intel AI Playground version v2.3.0 alpha or later from the official Intel website or authorized distribution channels
  3. Review the upgrade documentation provided by Intel before proceeding with the upgrade
  4. Perform a backup of any critical data and configurations related to AI Playground
  5. Install version v2.3.0 alpha or newer following Intel's recommended installation procedures
  6. After upgrade, verify that the default permissions have been correctly set and no longer allow unauthorized privilege escalation
  7. Confirm the installed version matches or exceeds v2.3.0 alpha
Caveat Review Intel release notes for v2.3.0 alpha to check for any feature changes or compatibility considerations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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