CVE-2026-34689
No exploitation reported by the sources we read.
- Published2026-09-22
- Fixed in12.12
- WeaknessCWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue does not require user interaction. Scope is changed.
Timeline
dates in UTC- 2026-09-2219:16CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.12 | < 12.12 | 12.12 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.5 | < 4.5 | 4.5 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As adobe, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Adobe Connectother versions: not affectedAffected
- ≤ 12.11no fix statedsemver
Not affected = 12.11.1, 12.12
- Adobe Connect Android Mobile Appother versions: not affectedAffected
- ≤ 4.4no fix statedsemver
Not affected = 4.5
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-22
Fix
- Update Adobe connect to 12.12
Advisories and patches
- helpx.adobe.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-09-24
- CNACVSS 3.18.6known since 2026-10-23
- CNAweakness (CWE)CWE-22known since 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-84785same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-r5qw-5gvq-mj8rsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- Published
- 2026-09-22
- Last Modified
- 2026-09-25
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-r5qw-5gvq-mj8r
Frequently asked questions
What is CVE-2026-34689?
Is CVE-2026-34689 actively exploited?
What is the CVSS score for CVE-2026-34689?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-r5qw-5gvq-mj8r
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0