CVE-2025-61830: Adobe Pass · Incorrect Authorization
Affects Adobe PassSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Pass | Affected
| Fixed in– |
AI-suggested
1. Restrict installation of SDKs to trusted sources only and enforce strict code signing policies to prevent malicious SDK deployment. 2. Implement application whitelisting and runtime protection to detect and block unauthorized SDKs or code injections. 3. Monitor logs and network traffic for unusual read/write operations within Adobe Pass components. 4. Educate users and developers about the risks of installing untrusted SDKs and enforce secure development lifecycle practices. 5. Apply any available patches or updates from Adobe promptly once released. 6. Use multi-factor authentication and least privilege principles around Adobe Pass integrations to limit potential damage. 7. Conduct regular security assessments and penetration testing focused on authorization mechanisms within Adobe Pass implementations.
Description
Adobe Pass versions 3.7.3 and earlier are affected by an Incorrect Authorization vulnerability. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and write access. Exploitation of this issue requires user interaction in that a victim must install a malicious SDK.