Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 1.28% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-76193High confidence
Adobe Campaign Classic (ACC) | Server-Side Request Forgery (SSRF) (CWE-918)
Adobe · Adobe Campaign Classic
Official source article: Adobe APSB26-134 ↗. Check the applicable product and release in the original source.
10.0CriticalCVSS 3.1
Within 72 hours
Patch availableCritical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Adobe Adobe Campaign Classic and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Patch available01
What, why and how
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.
What
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.
Why
The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.
Why
The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Server-Side Request Forgery (SSRF) → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-918 ↗
CWE-918: Server-Side Request Forgery (SSRF). The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Security update available for Adobe Campaign Classic | APSB26-134 →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026#202020 Adobe Security Bulletin Last updated on Aug 25, 2026 Security update available for Adobe Campaign Classic | APSB26-134 Bulletin ID Date published Priority APSB26-134 August 25, 2026 1 style grid width 12 Summary Adobe has released a security update for Adobe Campaign Classic. This update addresses critical
04
Evidence and provenance
Published 25 Aug 2026 · Last source change 29 Aug 2026, 23:57 UTC · CWE-918 · Server-Side Request Forgery (SSRF)
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-26
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-65617
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added patch: helpx.adobe.com/apsb26-134.html.psirt@adobe.com ↗
- Before
- remediation: helpx.adobe.com/apsb26-134.html
- After
- patch: helpx.adobe.com/apsb26-134.html · remediation: helpx.adobe.com/apsb26-134.html
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: helpx.adobe.com/apsb26-134.html.CNA ↗
- Before
- remediation: helpx.adobe.com/apsb26-134.html · vendor advisory: helpx.adobe.com/apsb26-134.html
- After
- remediation: helpx.adobe.com/apsb26-134.html
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: helpx.adobe.com/apsb26-134.html; added vendor advisory: helpx.adobe.com/apsb26-134.html; removed remediation: helpx-internal.corp.adobe.com/apsb26-134.html.helpx.adobe.com ↗
- Before
- remediation: helpx-internal.corp.adobe.com/apsb26-134.html
- After
- remediation: helpx.adobe.com/apsb26-134.html · vendor advisory: helpx.adobe.com/apsb26-134.html
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- ENISA EUVD mappingEUVD-2026-65617 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-65617"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.