Medium Input validation

CVE-2026-48308 — Premiere Pro | Improper Input Validation (CWE-20)

Premiere Pro is affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction. Scope is changed.

Published Jul 14, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: adobe

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Adobe

Premiere and 1 more

CVSS base

5.9

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Adobe Premiere, Adobe Premiere Pro).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Adobe	Premiere	≤ 26.2.2≤ 25.6.5	Vulnerable	CVE Program (cve.org) e CISA ADP
Adobe	Premiere Pro	≤ 25.6.5≥ 26.0 and ≤ 26.2.2	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

High

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.9	CVSS 3.1	Medium	1.4	4.0	psirt@adobe.com via NIST National Vulnerability Database
5.9	CVSS 3.1	Medium	—	—	adobe via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N (score shown at the top: psirt@adobe.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · adobe/premiere
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 5.9
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Jul 14, 2026 · adobe

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

helpx.adobe.com/security/products/premiere_pro/apsb26-76.html
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Adobe
every CVE for this vendor

Input validation
same class

CWE-20
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-34641 Premiere Pro | Out-of-bounds Write (CWE-787) Jul 31, 2026
High CVE-2026-48369 Premiere Pro | Out-of-bounds Write (CWE-787) Jul 14, 2026
High CVE-2026-48269 Premiere Pro | Heap-based Buffer Overflow (CWE-122) Jul 14, 2026
High CVE-2026-48270 Premiere Pro | Out-of-bounds Write (CWE-787) Jul 14, 2026
High CVE-2026-34637 Premiere Pro | Out-of-bounds Write (CWE-787) May 12, 2026
High CVE-2026-34638 Premiere Pro | Use After Free (CWE-416) May 12, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-48308 is "Premiere Pro | Improper Input Validation (CWE-20)", rated Medium. It affects Premiere (Adobe); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.