Subject: Security advisory: Java4Shell vulnerability (CVE-2026-114938). Published: 20 November 2026 | OpenAsset platform status: No customer impact
Start your security review
View & download sensitive information
ControlK

Welcome to OpenAsset's Trust Centre.

OpenAsset's commitment to data privacy and security is embedded in every part of our business. Our trust centre outlines the high-level details for several of the frameworks, regulations, and certifications that apply to our organisation and its products.

Use this Trust Centre to learn about our security posture and request access to our security documentation.

You can also contact security@openasset.com to report a security concern or potential vulnerability.

  • Clark Construction Group
  • BNIM
  • SmithGroup
  • Perkins&Will
  • Foster + Partners
  • Make Architects
  • Mace
  • BIG
  • CannonDesign
  • Kimley-Horn
  • Gensler
  • Balfour Beatty

Documents

OPENASSET | COMPLIANCESOC 2 Type 2

Trust Center Updates

Subject: Security advisory: Java4Shell vulnerability (CVE-2026-114938). Published: 20 November 2026 | OpenAsset platform status: No customer impact

Vulnerabilities

What’s happening

A critical vulnerability in the Java runtime, known as Java4Shell (CVE-2026-114938), has been disclosed. It’s a memory corruption flaw in the Base64 decoder of OpenJDK, the open-source core of most Java distributions. In some circumstances it can let an attacker run code remotely without authentication. It affects Java 17, 21, 25 and 27 from every vendor until fixed builds are applied. Java 8 and 11 are not affected. Exploitation also requires specific Intel or AMD server processors, and ARM-based systems are not affected. Fixed builds are available from Oracle, Amazon Corretto, Eclipse Temurin and other vendors.

Is the OpenAsset platform affected?

There is no impact to customers. We reviewed the OpenAsset platform, including OpenAsset Source digital asset management (Source, formerly the DAM), proposal management with OpenAsset Shred, the OpenAsset marketing website, and the infrastructure that hosts them. A small number of internal services used an affected Java version. None of them was exposed to the internet, and we have updated them to fixed versions. We have found no evidence of exploitation or compromise related to this vulnerability in our environment.

What you need to do

Nothing for your OpenAsset service. If your organisation runs its own Java applications, check them against your Java vendor’s advisory and apply the fixed build.

How we can help

We’re sharing this guidance to help our customers stay safe. This advisory is for information and doesn’t change any responsibilities under your agreement with us. For questions, contact our support team in-app, email support@openasset.com, or speak to your dedicated account manager.

Security advisory: PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) Published: 22 October 2026 | OpenAsset platform status: Not affected

Vulnerabilities

What’s happening

On 21 October 2026, the PHP project released fixes for 2 critical vulnerabilities in PHP, known as PHP2Shell. They allow unauthenticated remote code execution and affect all PHP installations that serve web requests. PHP powers a large share of the world’s websites, including many built on WordPress. Government agencies in the US and UK have urged organisations to update straight away.

Is the OpenAsset platform affected?

No. The OpenAsset platform does not run on PHP. That includes OpenAsset Source digital asset management (Source, formerly the DAM), proposal management with OpenAsset Shred, the OpenAsset marketing website, and the infrastructure that hosts them. We have found no evidence of exploitation or compromise related to these vulnerabilities in our environment.

If you use the OpenAsset WordPress plugin

https://wordpress.org/plugins/openasset/

The wordpress plugin runs inside your WordPress website, and WordPress runs on PHP. The vulnerabilities are in PHP itself, not in the plugin.

However, if your website runs an affected PHP version, it may be at risk. You or your hosting provider manage your website and its hosting, so these steps are for you or them.

Our recommended steps

Step 1. Check your PHP version: Ask your hosting provider or web developer which PHP version your site runs.

Step 2. Update PHP: Move to 8.5.12, 8.4.27, 8.3.36, or 8.2.35 or later, then restart your web server and PHP workers so the fix takes effect. If you’re on PHP 8.1 or older, contact your hosting provider about a backported fix or upgrade to a supported release.

Step 3. If you can’t update right away: The UK NCSC advises considering taking the system offline until it’s fixed. Putting your site into maintenance mode is a sensible stopgap.

Step 4. Check for signs of compromise: Ask your hosting provider to review your site for unexpected files, admin accounts, or changes.

Step 5. Rotate your OpenAsset API token after patching: The plugin connects to OpenAsset using an API token. One of these vulnerabilities can expose data held in server memory, which could include tokens. Once your site is patched:

  • Generate a new API token in OpenAsset.
  • Update the plugin settings with the new token.
  • Revoke the old token.

https://success.openasset.com/en/articles/6243971-generating-an-authentication-token-in-openasset

Rotate the token only after patching. Otherwise the new token faces the same exposure.

How we can help

We’re sharing this guidance to help our customers stay safe. Your WordPress website, its hosting, and its PHP version sit outside the OpenAsset platform, so we can’t manage, patch, or support them. This advisory is for information and doesn’t change any responsibilities under your agreement with us. For help updating PHP, contact your hosting provider or web developer. For help with your OpenAsset API token, contact our support team in-app, or via support@openasset.com, or your dedicated account manager.

Knowledge Base (FAQ)
  • How are user devices configured and secured?
  • What physical security controls are in place to protect systems and data?
  • Will my data be transferred or shared with any third parties?
  • Is data encrypted?
  • Do all users have unique ID's for access to production systems and data?
View more
If you need help using this Trust Center, please contact us.
Contact support
If you think you may have discovered a vulnerability, please send us a note.
Report issue
Built onSafeBase by Drata Logo