> For AI agents: this documentation is indexed at https://docs.united-security-providers.ch/usp-core-waap/llms.txt, and every page is available as markdown at its own address plus index.md.

# Core WAAP Release Notes

## 2.2.0 - 2026-10-29

### Contents

- core-waap proxy version: 2.2.0
- helm chart version: 2.2.0
- operator version: 2.2.0
- coreruleset version: 4.25.2

## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- **operator**: Add request header validation, which checks request headers for valid syntax and length.
  Individual headers can be excluded from the validation (`spec.coraza.headerValidation`).
  See [Header Validation](configuration/coraza/coraza-header-validation.md) for details.
- **operator**: The server name used for the TLS connection to a backend can now be set independently of the backend address.
  This allows reaching a backend via its internal name while it presents a certificate for its public name (`spec.routes[].backend.tls`).
- **operator**: OAuth 2.0 session cookies no longer cause false positives in the OWASP Core Rule Set (CRS).
- **operator**: The OAuth access token and ID token can now be withheld from the backend (`spec.authentications[].cookieConfigurations`).
- **operator**: Add options to control how the request ID (`x-request-id` header) is handled: keep the client-supplied ID (default),
  always generate a new one, or remove it (`spec.operation.requestId`).
- **operator**: The access log now also contains the original status code returned by the backend, even if an error page replaced the response.
- **operator**: Error pages can now be turned off for individual routes (`spec.routes[].errorPages`).
- **operator**: Error pages can now also depend on request or backend response headers, in addition to the status code.
  See [Error Mapping](configuration/error-mapping.md) for details.
- **operator**: Custom rules can now optionally be evaluated before the CRS rules.
- **helm**: Add options to set additional labels and annotations on the operator deployment and pod.

## Incompatible behavior changes

Changes that are expected to cause an incompatibility if applicable; deployment changes are likely required.

- **operator**: Header validation is enabled by default and blocks requests with invalid or overly long headers.
  It can be switched to log-only mode or disabled (`spec.coraza.headerValidation`),
  see [Introducing header validation](configuration/coraza/coraza-header-validation.md#introducing-header-validation).

## 2.1.3 - 2026-10-13

### Contents

- core-waap proxy version: 2.1.3
- helm chart version: 2.1.3
- operator version: 2.1.0
- coreruleset version: 4.25.1

## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- **proxy**: Updating Envoy proxy to version 1.39.4, addressing [various CVEs](https://github.com/envoyproxy/envoy/releases/tag/v1.39.4)

## 2.1.2 - 2026-10-12

### Contents

- core-waap proxy version: 2.1.2
- helm chart version: 2.1.2
- operator version: 2.1.0
- coreruleset version: 4.25.1

## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- **proxy**: Updating Envoy proxy to version 1.39.3, addressing various CVEs fixed in [1.39.2](https://github.com/envoyproxy/envoy/releases/tag/v1.39.2) and [1.39.3](https://github.com/envoyproxy/envoy/releases/tag/v1.39.3)

## 2.1.1 - 2026-08-31

### Contents

- core-waap proxy version: 2.1.1
- helm chart version: 2.1.1
- operator version: 2.1.0
- coreruleset version: 4.25.1

## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- **proxy**: Updating Envoy proxy to version 1.39.1, addressing [various CVEs](https://github.com/envoyproxy/envoy/releases/tag/v1.39.1)

## 2.1.0 - 2026-08-24

### Contents

- core-waap proxy version: 2.1.0
- helm chart version: 2.1.0
- operator version: 2.1.0
- coreruleset version: 4.25.1

## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- **operator**: Add support for using a alternative CRS version via OCI images, as well as loading OpenAPI and GraphQL schemas from OCI images.
- **operator**: Add support for multiple log formats (text / JSON) with customization options under `spec.operation.startup.logFormat`.
- **operator**: Add header manipulation capabilities.
- **operator**: Add cookies manipulation capabilities.
- **operator**: Add support for additional request size enforcement per route.
- **operator**: Add `timeout` setting for routes
- **operator**: Add possibility to set the location to redirect to after OpenID Connect / OAuth2 logout.
- **operator**: Deprecate `spec.coraza.validateJson` in favor of `spec.coraza.validateParsedBody`.
- **autolearning**: The processed CR is stripped of server-side fields that should not be sent back to Kubernetes.
- **autolearning**: The CLI allows mixed modes with log and/or CR/spec from file or Kubernetes.
- **autolearning**: The processed spec only adds/modifies what was learned and no longer turns implicit defaults into explicit settings.

## Incompatible behavior changes

Changes that are expected to cause an incompatibility if applicable; deployment changes are likely required.
It is advised to read the **[Core WAAP Migration Guide](operation/upgrade.md)** document for detailled configuration migration instructions.

- **operator**: Change default of `spec.coraza.requestBodyLimitAction` and `spec.coraza.responseBodyLimitAction` to `Reject`.
- **operator**: Header filter classes have changed. The class `MINIMAL` has been deprecated and is mapped
  to a new and slightly less restrictive class `RESTRICTED`. A new, more permissive class `EXTENDED` has been added.
  The headers contained in the existing classes (`RESTRICTED`, `STANDARD` and the response class) have also
  partially changed. For what changed in detail see the **[Core WAAP Migration Guide](operation/upgrade.md)**.

## 2.0.2 - 2026-06-24

This is a security release that updates core-waap proxy.

### Contents

- core-waap proxy version: 2.0.2
- helm chart version: 2.0.2
- operator version: 2.0.0
- coreruleset version: 4.18.0

## Bug fixes

Changes expected to improve the state of the world and are unlikely to have negative effects.

- **proxy**: Updating envoy proxy to version 1.37.5, addressing [various CVEs](https://github.com/envoyproxy/envoy/releases/tag/v1.37.5)

## Known issues

- **coraza**: There is a [known issue](https://github.com/corazawaf/coraza/issues/1611) regarding `ProcessPartial` and body validation.

## 2.0.1 - 2026-06-04

This is a security release that updates core-waap proxy.

### Contents

- core-waap proxy version: 2.0.1
- helm chart version: 2.0.1
- operator version: 2.0.0
- coreruleset version: 4.18.0

## Bug fixes

Changes expected to improve the state of the world and are unlikely to have negative effects.

- **autolearning**: Fix CLI not finding the right resource when a kubernetes source was used.
- **proxy**: Updating envoy proxy to version 1.37.3, addressing CVE-2026-47774 HTTP/2 bomb

## Known issues

- **coraza**: There is a [known issue](https://github.com/corazawaf/coraza/issues/1611) regarding `ProcessPartial` and body validation.

## 2.0.0 - 2026-04-02

### Contents

- core-waap proxy version: 2.0.0
- helm chart version: 2.0.0
- operator version: 2.0.0
- coreruleset version: 4.18.0


## New features and improvements

Newly added capabilities/functionality or enhancements to existing features, such as better performance, usability, stability, or efficiency.

- Changed extension mechanism and optimized all features internally to reduce memory requirements and improve performance.
- **proxy**: Add new optional proxy executable with debug support. See [debugging](operation/debugging.md) for details on how to use it.
- **documentation**: Add new documentation for [debugging](operation/debugging.md) which describes the recommended approach for debugging crashes, segmentation faults and other issues you might encounter.
- **helmchart**: Reduce permissions for the default `ClusterRole` used by the operator to enhance security and align
  with the principle of least privilege.
- **helmchart**: Add the ability to configure `securityContext` for the operator.
- **operator**: Add the ability to configure `securityContext` for all containers through
  the operator's YAML configuration file.
- **operator**: Add rate limiting feature for repeat offenders,
  see `spec.rateLimiting.repeatOffender`.
- **operator**: Add support for Core WAAP debug image.
- **operator**: Add support for disabling performance optimizations for coraza.
- **openapi**: Add support for OpenAPI 3.2 and OpenAPI Overlays 1.1.0.
- **header_filter**: Add new configuration option `denyPatternsResponse` to filter response headers based on regular expressions.
- **header_filter**: Add support for per-route filter configuration.
- **header_filter**: Add option to explicitly deny headers for requests / responses.
- **header_filter**: Add option to deny header values by pattern for responses.
- **dos_prevention**: First release.
- **coraza**: Improve performance when dealing with larger HTTP bodies.


## Bug fixes

Changes expected to improve the state of the world and are unlikely to have negative effects.

- **header_filter**: Fix typo in default response header class.


## Incompatible behavior changes

Changes that are expected to cause an incompatibility if applicable; deployment changes are likely required.
It is advised to read the **[Core WAAP Migration Guide](operation/upgrade.md)** document for detailled configuration migration instructions.

- **proxy**: Authentication cookies will now include a unique suffix to prevent them from overwriting one another.
- **helmchart**: The docker image has been renamed to **usp-core-waap-proxy**.
- **helmchart**: Removed all traffic processing related settings; there are no longer sidecars for ICAP and OpenAPI.
- **helmchart**: Removed all metrics related settings; all metrics are now handled in the main container
- **operator**: Removed legacy CRS settings under `spec.crs`; use the newer `spec.coraza.crs` settings instead.
- **operator**: Improved and extended header filtering, now also configurable per route.
  See the new settings under `spec.headerFilter` and per-route references at `spec.routes[].headerFilterRef`.
  Please consult the documentation for details on filter operation and merge behavior.
- **operator**: The type of `spec.operation.startup.additionalCliArgs` changed from `string` to `[]string`.
- **operator**: The envoy admin interface now binds to localhost (127.0.0.1) by default.
  It will only bind to 0.0.0.0 when explicitly enabled.
- **operator**: Removed metrics sidecar and all related settings; all metrics are now handled in the main container.
- **openapi**: Return 403 instead of a 400 when a request fails validation


## Removed config or runtime

Normally occurs at the end of the deprecation period. It is advised to read the
**[Core WAAP Migration Guide](operation/upgrade.md)** document for detailled configuration migration instructions.

- **helmchart**: Removed all traffic processing related settings; there are no longer sidecars for ICAP and OpenAPI.
- **helmchart**: Removed all metrics related settings; all metrics are now handled in the main container.
- **operator**: Removed legacy CRS settings under `spec.crs`; use the newer `spec.coraza.crs` settings instead.
- **operator**: Removed `spec.trafficProcessing` settings; ICAP and OpenAPI settings are now under `spec.icap` resp. `spec.openapi`.
- **operator**: Removed all metrics related settings; all metrics are now handled in the main container.
- **operator**: Replaced `spec.headerFiltering` with `spec.headerFilter` with slightly changed settings.

## Known issues

- **coraza**: There is a [known issue](https://github.com/corazawaf/coraza/issues/1611) regarding `ProcessPartial` and body validation.
