dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-12813

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was detected in activepieces up to 0.83.0. This vulnerability affects the function handleUrlFile in the library packages/server/engine/src/lib/variables/processors/file.ts of the component File URL Handler. The manipulation results in server-side request forgery. The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the File URL Handler component of ActivePieces up to version 0.83.0. The vulnerable function handleUrlFile in the file processing module allows remote attackers to manipulate URL inputs to make the server perform arbitrary HTTP requests to internal or external resources.

MitigationUpgrade to a version beyond 0.83.0 when available; as an interim control, implement strict URL allowlisting, disable the file URL fetching feature if not required, and apply network segmentation to prevent the server from reaching internal services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ActivePieces is installed
    Check for ActivePieces processes, Docker containers, or installation directories. Common paths: /opt/activepieces, /home/user/activepieces, or docker ps for activepieces container.
    Affected if ActivePieces software is found running in the environment
  2. Determine the ActivePieces version
    Check the installed version via: docker images (image tag), package.json version field, or the /api/health endpoint response which may include version info. Compare against affected range: versions 0.83.0 and below.
    Affected if Installed version is 0.83.0 or lower
  3. Verify the File URL Handler is accessible
    Identify if the handleUrlFile function is exposed. This is typically accessed via API endpoints handling file/url imports. Check API routing configuration or attempt a test request to file-related endpoints with a URL parameter.
    Affected if The file URL fetching feature is enabled and the API endpoint is accessible
  4. Confirm network outbound access
    Inspect server firewall rules, proxy configuration, or network policies to determine if the ActivePieces server can make outbound HTTP/HTTPS requests to arbitrary addresses.
    Affected if The server has unrestricted outbound network access allowing potential SSRF targets

You are affected if ActivePieces version 0.83.0 or lower is installed AND the file URL handler feature is exposed and accessible, combined with the ability for the server to make outbound HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version beyond 0.83.0 when available; as an interim control, implement strict URL allowlisting, disable the file URL fetching feature if not required, and apply network segmentation to prevent the server from reaching internal services.

Recommended fix Moderate confidence

Latest stable release of activepieces (version > 0.83.0)

  1. 1. Identify the current version of activepieces installed in your environment
  2. 2. If the current version is 0.83.0 or earlier, plan an upgrade to a version newer than 0.83.0
  3. 3. Before upgrading in production, test the new version in a staging environment to ensure compatibility with your existing flows and integrations
  4. 4. Perform a full backup of your activepieces instance including database and configuration
  5. 5. Upgrade activepieces to the latest stable release (preferably a version significantly newer than 0.83.0 to ensure the SSRF fix is included)
  6. 6. Verify the handleUrlFile function behavior after upgrade to confirm the vulnerability is addressed
  7. 7. Monitor for any unusual outbound requests from the server that might indicate attempted exploitation
Caveat Review release notes between your current version and the target version for any breaking changes related to file processing or variable handling

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data