LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36059: Adobe Bridge Memory Corruption Vulnerability Could Lead to Arbitrary Code Execution

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

This vulnerability affects Adobe Bridge 11.1 and earlier. A malicious Bridge file could corrupt memory and let code run as the logged-in user, but the user must open the file. Business risk is workstation compromise, especially for creative or marketing users handling files from outside parties.

Executive priority

Treat as a high-priority workstation patching item, not an internet-wide emergency. Focus on users who process external creative files because compromise runs with their account privileges.

Technical view

CVE-2021-36059 is a high-severity Adobe Bridge memory corruption issue classified as CWE-788. The CVSS 3.1 vector is local, low complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to endpoints with Adobe Bridge 11.1 or earlier installed, particularly systems receiving external project, asset, or Bridge-related files.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires user interaction with a malicious Bridge file and could execute code in the current user's context.

Researcher notes

Evidence is limited to CVE data and Adobe's referenced advisory. No CPEs or exact fixed version are included in the provided bundle. The key constraints are local attack vector, required user interaction, and execution in the current user context.

Mitigation direction

  • Identify systems running Adobe Bridge 11.1 or earlier.
  • Review Adobe APSB21-69 for the applicable vendor update guidance.
  • Prioritize updates on workstations handling external creative assets.
  • Restrict opening untrusted Bridge files until updated.
  • Apply endpoint controls for suspicious file delivery and execution.

Validation and detection

  • Inventory Adobe Bridge installations and versions across managed endpoints.
  • Confirm whether each installation is version 11.1 or earlier.
  • Check Adobe APSB21-69 for the vendor-stated remediation path.
  • Validate that updated endpoints no longer report affected Bridge versions.
  • Review security telemetry for suspicious file-open events involving Bridge.
Prepared
Confidence
high
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-36059 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-36059Attack 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.