CVE-2023-22244
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 · uneditedAdobe Premiere Rush version 2.6 (and earlier) is affected by a Use After Free 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 confidenceAdobe Premiere Rush version 2.6 and earlier contains a Use After Free vulnerability. This memory corruption flaw allows arbitrary code execution when a user opens a malicious file, with the code executing in the context of the current user account.
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<= 2.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if Adobe Premiere Rush is installedOn Windows, check Program Files/Adobe/Adobe Premiere Rush or the system registry under Uninstall entries. On macOS, check /Applications for Adobe Premiere Rush. Alternatively, search for the application in the system search bar.Affected if Premiere Rush is found installed on the system
-
Determine the installed Premiere Rush version numberOpen Adobe Premiere Rush and navigate to Help > About (or the application menu on macOS). The version number displays in the about window. On Windows, you may also find version information in the Windows Programs and Features list or registry uninstall entries.Affected if Version cannot be determined or the application is not found
-
Compare your installed version against the affected rangeNote the full version number (e.g., 2.6, 2.5.1, 1.5) from the About screen. Compare numerically to the affected threshold of version 2.6. Any version 2.6 or lower (including all 2.x versions before 2.6, and 1.x versions) falls within the vulnerable range.Affected if The installed version is 2.6 or any earlier version (e.g., 2.5, 2.0, 1.5)
If Adobe Premiere Rush is installed and the version is 2.6 or earlier, the environment is affected by this Use After Free vulnerability.
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 · scopedUpdate Adobe Premiere Rush to a version newer than 2.6. Avoid opening untrusted or unexpected media files from unverified sources.
Premiere Rush version > 2.6
- 1. Close Adobe Premiere Rush if it is currently running
- 2. Open the Creative Cloud desktop application or navigate to adobe.com
- 3. Locate Adobe Premiere Rush in your installed applications
- 4. Check for and install any available updates
- 5. Verify the installed version is greater than 2.6 after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22244 — 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-2023-22244 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