LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36078: Adobe Bridge PDF File Parsing Memory Corruption Remote Code Execution Vulnerability

Adobe Bridge version 11.1 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious Bridge file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-36078 is a high-severity Adobe Bridge flaw where opening a malicious file could let an attacker run code as the signed-in user. It requires user interaction, so risk is highest on creative workstations that receive or open untrusted files.

Executive priority

Treat as a high-priority workstation remediation issue, especially in creative or marketing environments. It is not shown as actively exploited in the provided sources, but successful exploitation could compromise data and systems under the user's privileges.

Technical view

Adobe Bridge 11.1 and earlier are affected by a memory corruption issue, mapped to CWE-788, in malicious file handling. CVSS 3.1 is 7.8 with local attack vector, low complexity, no privileges, required user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to endpoints with Adobe Bridge 11.1 or earlier installed. The bundle does not provide complete product CPEs or corrected version details, so asset inventory and Adobe guidance are needed to confirm scope.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires convincing a user to open or process a malicious file in Adobe Bridge, with resulting code execution in that user's context.

Researcher notes

Evidence is limited to the CVE record, CVE List data, and Adobe advisory reference. Do not assume broader Adobe products are affected. The CVSS vector is local with user interaction, which should guide realistic exposure scoring and validation.

Mitigation direction

  • Inventory endpoints for Adobe Bridge installations and versions.
  • Check Adobe APSB21-69 for the corrected release and deployment guidance.
  • Prioritize update deployment for users handling external media files.
  • Limit opening untrusted files in Bridge until remediation is confirmed.
  • Use endpoint controls to reduce impact from user-context code execution.

Validation and detection

  • Confirm whether Adobe Bridge version is 11.1 or earlier.
  • Verify patched systems report a vendor-supported corrected Bridge version.
  • Review EDR alerts for suspicious child processes from Adobe Bridge.
  • Confirm creative teams understand restrictions on untrusted files.
  • Document any systems that cannot be updated immediately.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-788: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36078 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-36078Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeBridgeunspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-788 · source CWE mapping

Access of Memory Location After End of Buffer

Access of Memory Location After End of Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.