dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-39576

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Unauthenticated PHP Object Injection in SingleMalt <= 1.5 versions.

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

Unauthenticated PHP Object Injection in SingleMalt <= 1.5 allows remote attackers to inject malicious PHP objects via unsafe deserialization without authentication, potentially leading to remote code execution depending on available POP gadgets in the application or included libraries.

MitigationUpgrade to a version newer than 1.5 that includes the security patch, or audit and replace all unsafe unserialize() calls with json_decode() or similar safe deserialization methods.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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. Identify SingleMalt installation and version
    Locate the SingleMalt application on your system and check the version number (typically in a version file, README, or within the main PHP files)
    Affected if The installed version is 1.5 or lower
  2. Find unsafe deserialization calls
    Search the codebase for PHP files containing unserialize() function calls, particularly in user input handling paths
    Affected if Code contains unserialize() calls that process unauthenticated user input
  3. Verify unauthenticated access exposure
    Check the application's authentication configuration and routing to determine if certain endpoints are accessible without authentication
    Affected if The vulnerable deserialization code path can be reached without any authentication
  4. Check for POP gadget libraries
    Examine the application's included libraries and dependencies for classes that could be exploited as PHP Object Injection gadgets (common libraries like Doctrine, Symfony, Propel, etc.)
    Affected if The application includes libraries with exploitable POP gadget classes

You are affected if SingleMalt version 1.5 or lower is installed and the application exposes unserialize() calls on unauthenticated user input, especially if POP gadget libraries are present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version newer than 1.5 that includes the security patch, or audit and replace all unsafe unserialize() calls with json_decode() or similar safe deserialization methods.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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