ServiceStack Security

ServiceStack publishes product security information and version-specific software inventories for customers and suppliers assessing their use of ServiceStack. This section is the public reference for product security, vulnerability reporting, software inventories, assessment evidence and EU Cyber Resilience Act (CRA) readiness. Customers and suppliers can use https://docs.servicestack.net/security/ as a single entry point.

All source code for ServiceStack's NuGet packages is public, including the full history of every change. Packages are built and published to NuGet.org by public GitHub Actions workflows using NuGet Trusted Publishing, so each release can be traced to a public commit and the public run that built it. See open source and verifiable publishing.

Published Security Advisories

Disclosed vulnerabilities, affected versions and fixes are published as GitHub Security Advisories.

View Advisories →

Supplier review evidence​

The supplier assurance directory maps common policy, certification, audit, development, regulatory and lifecycle questions to public evidence and current status. The information security policy provides our public policy summary.

Requested information Public information and evidence
Software Bill of Materials (SBOM) Download release security bundles and verify their contents
Vulnerability Exploitability eXchange (VEX) Availability, interpretation and version scope
Penetration test report or executive summary Published assessments and current report availability
Whether CE marking will be applied where required CRA readiness and CE-marking position
Vulnerability reporting and coordinated disclosure ServiceStack security policy

These pages and the published evidence are provided in English. Customers can reference them in supplier assessments without requesting copies of internal company policies.

Explore security information​

Match evidence to the software you use​

Identify the NuGet package ID, exact package version and target framework used by your application. If you receive DLLs through another vendor, also establish which package or private build produced them. An assembly filename alone does not identify a release or its resolved dependencies.

For example, the following commonly embedded components are covered by the corresponding package entries in the published 10.5.0 and 10.4.2 bundles:

Component NuGet package ID
ServiceStack.Common.dll ServiceStack.Common
ServiceStack.Interfaces.dll ServiceStack.Interfaces
ServiceStack.OrmLite.dll ServiceStack.OrmLite
ServiceStack.OrmLite.Sqlite.dll ServiceStack.OrmLite.Sqlite
ServiceStack.Text.dll ServiceStack.Text

Use the bundle's index.json, package mapping and per-release manifests to identify the included products. The bundle is broader than this example list.

An SBOM for one release is not evidence for a different release. NuGet dependency ranges also allow an integrating application to resolve different dependency versions. Maintain an application-level inventory alongside the ServiceStack package inventory, including the database provider, native dependencies and deployed .NET runtime where applicable.

Published evidence status​

Last checked: 14 November 2026.

Report a vulnerability privately​

Follow the security policy and use GitHub private vulnerability reporting or the security reporting portal. Please use one channel and keep undisclosed vulnerability details out of public issues.

Public evidence is scoped to the products and versions it identifies. Confidential investigation details, infrastructure inventories and internal risk records are not part of the public assurance bundle.