Bridge vulnerabilitiesRanked by how likely they are to be used.
Bridge is made by Adobe. We track 127 published vulnerabilities listed under that exact name, across 44 versions. None of them is on the list of flaws known to be exploited today. Adobe lists newer releases under their own names, such as Bridge CC, so check those pages too.
We keep watching the known-exploited list.
Is Bridge listed under other names? Yes.
Adobe also lists Bridge under more specific names, such as Bridge CC. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Bridge vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Bridge's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Bridge flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 19%CVE-2015-3111Critical
Heap-based buffer overflow in Adobe Photoshop CC before 16.0 (aka 2015.0.0) and Adobe Bridge CC before 6.11 allows attackers to execute arbitrary code via unspecified vectors.
- 17%CVE-2015-3110Critical
Integer overflow in Adobe Photoshop CC before 16.0 (aka 2015.0.0) and Adobe Bridge CC before 6.11 allows attackers to execute arbitrary code via unspecified vectors.
- 14%CVE-2015-3112Critical
Adobe Photoshop CC before 16.0 (aka 2015.0.0) and Adobe Bridge CC before 6.11 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
- 7.8%CVE-2024-20752High
Bridge versions 13.0.5, 14.0.1 and earlier are affected by a Use After Free vulnerability that could result in arbitrary code execution in the context of the current user.
- 7.5%CVE-2021-36073High
Adobe Bridge version 11.1 (and earlier) is affected by a heap-based buffer overflow vulnerability when parsing a crafted .SGI file.
- 7.5%CVE-2021-36075High
Adobe Bridge version 11.1 (and earlier) is affected by a Buffer Overflow vulnerability due to insecure handling of a malicious Bridge file, potentially resulting in arbitrary code execution in the context of the...
- 7.2%CVE-2021-28624High
Adobe Bridge version 11.0.2 (and earlier) are affected by a Heap-based Buffer overflow vulnerability.
- 5.8%CVE-2020-9552High
Adobe Bridge versions 10.0 have a heap-based buffer overflow vulnerability.
- 5.3%CVE-2020-9562High
Adobe Bridge versions 10.0.1 and earlier version have a heap overflow vulnerability.
- 5.2%CVE-2020-9555High
Adobe Bridge versions 10.0.1 and earlier version have a stack-based buffer overflow vulnerability.
Running Bridge? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Heap-based buffer overflow in Adobe Photoshop CC before 16.0 (aka 2015.0.0) and Adobe Bridge CC before 6.11 allows attackers to execute arbitrary code via unspecified vectors.
- Matched to
- Bridge on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 127 published vulnerabilities listed under the name Bridge, across 44 versions.
None of Bridge's vulnerabilities is on the list of flaws known to be exploited today.
Adobe also lists Bridge under more specific names, such as Bridge CC. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a EdgeProtect account and track Bridge. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.