"Solid upgrades the web. It's a better vision for data security and privacy."
- Bruce Schneier, Inrupt Chief of Security Architecture

Security Vulnerability Reporting

Inrupt's Product Security Incident Response Team (PSIRT) values the work of security researchers and welcomes reports of any vulnerabilities or security concerns in our software or our website.

How to report

Please use one of the following options:

  • Submit an issue through our Service Desk. Choose Commercial Support if you are an Inrupt customer, or Community Support if not.
  • Email security@inrupt.com. For sensitive details, please encrypt your message using our PGP public key.

To help us investigate quickly, please include a description of the issue, the affected product or URL and version, steps to reproduce, and any proof-of-concept code or screenshots.

What to expect

  • We will confirm receipt of your report within 2 business days.
  • We will share our assessment and an estimated resolution timeline.
  • We will let you know when a fix is available and, with your permission, credit you in our Acknowledgements.

Testing guidelines

To protect our customers and stay within the law, please do not do the following without prior written authorization from PSIRT:

  • Denial of service (DoS) testing of any kind
  • High-volume automated scanning
  • Accessing, modifying, or deleting data that does not belong to you

To request authorization for this kind of testing, contact security@inrupt.com.

Third-Party Components

Inrupt software includes third-party and open source components. We update these components to the latest compatible versions as part of our regular release cycle.

A vulnerability in a third-party component does not necessarily mean Inrupt software is affected, since that depends on how the component is used. If you have questions about whether a specific CVE affects Inrupt, please contact PSIRT at security@inrupt.com before submitting a report.

We assess risk using CVSS v4.0 scoring.

Security Advisories

We publish advisories for confirmed vulnerabilities that resulted in, or could result in, a security incident, whether in a service Inrupt runs or in a customer's deployment of our software. Each advisory describes the issue and how it was resolved. View our security advisories.

Security advisories and other security content are provided "as is," without guarantee or warranty of any kind. Your use of this information, or of any linked material, is at your own risk. Inrupt may change or update this content at any time without notice.

PGP Public Key

Use the Inrupt Security Team PGP public key to encrypt sensitive information you send to security@inrupt.com and to verify that messages from us are authentic.

Created
04/04/2025
Expiry
04/03/2027
Algorithm
RSA
Key Size
4096
Fingerprint
A0C4615E02AF85F5141D7F77120A48998DE08BDC
UID
PGP Key

Acknowledgements

Thank you to the following researchers for responsibly reporting vulnerabilities to Inrupt:

  • Justin Richer, Bespoke Engineering
  • Othmar Lechner
  • Christoph Braun, Karlsruhe Institute of Technology (KIT), Institute AIFB, Web Science (github.com/uvdsl)