dbcve.org
AuditionApplication · Adobe

CVE-2026-48365

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 25.6.6 / 26.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges 5 weeks old

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
Audition is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

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

Adobe Audition contains an out-of-bounds write vulnerability in its file parsing logic. When processing a specially crafted malicious file, the application writes data beyond the allocated buffer boundaries, allowing an attacker to overwrite adjacent memory and achieve arbitrary code execution in the context of the current user.

MitigationDo not open untrusted or unexpected files in Adobe Audition. Keep Adobe Audition updated with the latest security patches from Adobe. Deploy endpoint detection and response (EDR) solutions capable of detecting suspicious process behavior and fileless attacks.

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
AuditionApplication
Affected:< 25.6.6>= 26.0, < 26.3

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

CVSS:3.1/AV:L/AC:L/PR:N/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. Verify Adobe Audition is installed
    Check for Adobe Audition installation: On Windows, look in C:\Program Files\Adobe\Adobe Audition* or check Registry key HKLM\SOFTWARE\Adobe\Audition. On macOS, check /Applications/Adobe Audition* or ~/Library/Application Support/Adobe/Audition
    Affected if Adobe Audition is not installed on the system
  2. Determine installed Adobe Audition version
    Open Adobe Audition and go to Help > About Adobe Audition, or check the Windows Registry at HKLM\SOFTWARE\Adobe\Audition\InstallPath\Version, or examine the audition.exe file properties on disk for the version attribute
    Affected if Unable to determine the installed version for comparison
  3. Compare version against affected ranges
    Compare your installed version to the affected ranges: versions below 25.6.6 (such as 25.0 through 25.6.5) AND versions 26.0 through 26.2.x are vulnerable. Versions 25.6.6 and above, and 26.3 and above, are not affected
    Affected if Installed version falls below 25.6.6 OR is 26.0 through 26.2.x (any minor/patch version)
  4. Identify file parsing usage context
    Determine if the system or user profile contains audio project files (.sesx, .pkf) that could contain specially crafted content, or if users routinely open audio files from untrusted sources in Adobe Audition
    Affected if Users routinely process audio files from untrusted or unknown sources in Adobe Audition

A system is affected if Adobe Audition version is either below 25.6.6 or falls within the 26.0 to 26.2.x range, and users open audio files in the application.

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 25.6.6 / 26.3 or later
Fixed in 25.6.626.3
Interim mitigation

Do not open untrusted or unexpected files in Adobe Audition. Keep Adobe Audition updated with the latest security patches from Adobe. Deploy endpoint detection and response (EDR) solutions capable of detecting suspicious process behavior and fileless attacks.

Recommended fix Moderate confidence

Upgrade to Adobe Audition 25.6.6 (for 25.x branch) or 26.3+ (for 26.x branch); prefer latest 26.x release

  1. 1. Open Adobe Creative Cloud desktop application or navigate to the Adobe Audition download page
  2. 2. Check your current Adobe Audition version by opening Audition and going to Help > About Adobe Audition
  3. 3. If running version 25.x (< 25.6.6), update to version 25.6.6 or later
  4. 4. If running version 26.x (< 26.3), update to version 26.3 or later
  5. 5. Alternatively, download the latest version from Adobe's official website to ensure all security patches are included
  6. 6. After updating, verify the version number matches a fixed release (25.6.6 or higher, or 26.3 or higher)
Caveat Standard Adobe update considerations: ensure system meets requirements, back up user presets/projects as precaution

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

Fix this in Audition Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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