Welcome to the FormAssembly Trust Center Portal
This is your go-to place for everything related to security, privacy, and compliance on our platform. We know that trust matters, especially when you're handling sensitive data. That’s why we built this space to give you a clear look at how we manage and protect your information.
Here, you’ll find detailed resources like our security certifications, compliance documents, data protection policies, third-party audit reports, incident response steps, and more. It's meant to keep you informed and give you peace of mind.
Please note: Some of our policies and documents are only available to prospect and current Team, Enterprise, or Government Cloud customers. If that applies to you and you need access, please reach out to your assigned Customer Success Manager or contact our Support Team.
- Are customer-supplied encryption keys supported?
- Does your organization have a Data Sanitization Policy?
- Describe the encryption method used for data at rest.
- Has your company experienced a security breach in the last 2 years? If so, please describe what happened and the mitigations put in place.
- How does your API manage access?
Trust Updates
Security Advisory: Recent PHP Vulnerabilities - FormAssembly Not Affected
The PHP project recently disclosed several security vulnerabilities. FormAssembly reviewed each of them against our assets.
CVEs reviewed:
- CVE-2026-115560
- CVE-2026-126714
- CVE-2026-129289
- CVE-2026-129496
- CVE-2026-129182
- CVE-2026-129474
- CVE-2026-129481
- CVE-2026-129291
Assessment: FormAssembly is not affected by any of these vulnerabilities. The conditions needed to exploit them depend on specific PHP session, FastCGI and logging configurations, and FormAssembly's production environment does not use those configurations.
Next steps: Following security best practices, FormAssembly will still apply the updated PHP releases as a precaution. We don't expect any service disruption, and you don't need to do anything.
Security Advisory: NGINX HTTP/2 Vulnerabilities (CVE-2026-123633, CVE-2026-123007) - FormAssembly Not Affected
Two security vulnerabilities were recently disclosed in NGINX's HTTP/2 implementation.
CVEs reviewed:
Assessment: FormAssembly is not affected. These vulnerabilities can only be exploited when HTTP/2 is enabled. FormAssembly reviewed every NGINX asset in our environment and confirmed that none of them have HTTP/2 enabled.
Next steps: You don't need to do anything. We will keep monitoring vendor advisories and apply updates in line with our standard patching process.
Security Advisory: Java4Shell (CVE-2026-114938) - FormAssembly Not Affected
A security vulnerability affecting Java was recently disclosed. FormAssembly reviewed our assets to check for any exposure.
CVE reviewed:
Assessment: FormAssembly is not affected. FormAssembly team confirmed that the FormAssembly application our customers use does not use Java in any part of its environment, so this vulnerability doesn't apply.
Next steps: You don’t need to do anything. We will keep monitoring security advisories as part of our ongoing vulnerability management program.
PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619)
Update October 23, 2026 4:55pm EDT
As our earlier update noted, FormAssembly has completed updates and mitigation on 10/21 for these vulnerabilities across our plan types, including Federal. We continue to review and monitor our platform services, as well as supply chains, and will keep our customers updated.
No action is needed from you. We will continue to monitor and share updates, including on the availability status of our template library.
Update October 22, 2026 7:25pm EDT
As our earlier update noted, FormAssembly has completed updates and mitigation on 10/21 for these vulnerabilities across our plan types, including Federal. We're assessed our subprocessors and service providers, who do not appear impacted; but we continue to monitor across our supply chain.
No action is needed from you. We will continue to monitor and share product service updates through service notifications in FormAssembly and from our Customer Support team on the availability status of our template library.
Update October 22, 2026 10:40am EDT
FormAssembly has completed updates and mitigation as of 8:00pm EDT 10/21 for these vulnerabilities across our plan types, including Federal.
We continue to monitor, and have no indicators of attempted successful exploit or that customer data has been affected, checking against earlier dates prior to the vulnerability details becoming public. We have completed our assessment of subprocessors and primary/secondary service providers against these vulnerabilities, and do not appear affected. We're continuing to review our downstream supply chains.
No action is needed from you, and we’ll continue to update our security statement as remediation progresses. The FormAssembly template library may be temporarily unavailable, including the “More” tab and FormAssembly-provided templates. Your own private and shared templates and forms keep working as usual. We anticipate the feature being restored shortly once our deployments have completed.
We will continue to monitor and share product service updates through this portal and service notifications in FormAssembly.
Update October 21, 2026 6:45pm EDT
FormAssembly has been implementing remediation as of this afternoon. We have no indicators of attempted successful exploit or that customer data has been affected, checking against earlier dates prior to the vulnerability details becoming public. We have also assessed our subprocessors and primary service providers against these vulnerabilities, and do not appear affected. We're continuing to review our secondary service providers and downstream supply chains.
No action is needed from you, and we’ll continue to update our security statement as remediation progresses. While we deploy, the FormAssembly template library may be temporarily unavailable, including the “More” tab and FormAssembly-provided templates. Your own private and shared templates and forms keep working as usual. We anticipate the feature being restored shortly once our deployments have completed.
PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619)
Status: In progress. Last updated October 21, 2026 2:45pm EDT
Background
On October 21, 2026, the PHP project disclosed two critical vulnerabilities in PHP, one of the technologies FormAssembly is built on. You trust us with your data, and we want to be open with you about what this means and what we're doing.
- CVE-2026-109618: PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
See also https://www.cve.org/CVERecord?id=CVE-2026-109618 - CVE-2026-109619:PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).
See also https://www.cve.org/CVERecord?id=CVE-2026-109619
What we're doing
Our engineering and infrastructure teams have assessed the exposure and have begun work to address these vulnerabilities across all of FormAssembly's environments. We will add updates here as each step is completed.
What you need to do
Nothing. FormAssembly is fully available, and no action is needed on your part. FormAssembly will continue to remediation efforts.
We will update this page as work progresses and when remediation is complete. If you have questions, our team is glad to help
FormAssembly Not Affected by Compromised Axios Package
FormAssembly Not Affected by Compromised Axios Package
We are aware of a recently disclosed supply chain incident affecting specific versions of the widely used npm package axios.
What happened?
Certain versions of axios were found to include malicious code introduced through a compromised maintainer account.
Affected versions:
axios@1.14.1axios@0.30.4
Our status
We have conducted an internal review and can confirm that FormAssembly systems and services are not affected by these compromised versions.
We continue to monitor this situation closely and will provide updates if necessary.
For more details, you may refer to:
https://semgrep.dev/blog/2026/axios-supply-chain-incident-indicators-of-compromise-and-how-to-contain-the-threat/







