---
schema_version: "1"
id: 885ff0353796f1bbf54bfe2c6de4ba9a996923b1f806fe8808b71acbf2eb7e39
title: JSON Threat Protection
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/policies/json-threat-protection-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/policies/json-threat-protection-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1902e80a9cf8ecc0cffc504e0d48f23c926b15483cad45be07dd4102c626680d
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
keywords: mule, json, threat, protection, policy, release notes
---

# JSON Threat Protection

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

## 1.2.2

**October 1, 2026**

### What’s New

- This release updates policy metadata only. There’s no functional change.

## 1.2.0

**March 15, 2023**

### Minimum Mule Version

**Mule 4.1.0**

### What’s New

- You can now write a sequence of numbers followed by a blank space when creating a policy.

- The policy definition and policy implementation file are now separate. This enables stronger
  validations for policy configuration parameters.

## 1.1.5

**Jun 1, 2022**

### Minimum Mule Version

**Mule 4.1.0**

### Fixed issues

- Policy considered valid a payload containing multiple JSON objects.

## 1.1.4

**Apr 30, 2020**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

- Performance improvements are introduced to the header manipulation engine.

### Fixed issues

- After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of
  case-sensitivity:

  [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).

## 1.1.3

**Jul 24, 2019**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

Several performance improvements are introduced in this release.

### Fixed Issues

When a malformed JSON was provided, the JSON threat protection exposed the names of the internal
classes. This issue is now resolved.

## 1.1.2

**Apr 26, 2019**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

Several performance improvements are introduced in this release.

## 1.1.1

**Jun 25, 2018**

### Minimum Mule Version

**Mule 4.1.0**

### New Features and Enhancements

- Added `violationCategory` in the YAML configuration for Feedback Loop.

## 1.1.0

**Jan 25, 2018**

### Minimum Mule Version

**4.1.0**

### New Features and Enhancements

Reduced error-handling verbosity in templates.

### Fixed Issues

When a WSDL proxy received an empty payload, or an invalid XML, an ExpressionRuntimeException error
was generated. This issue is now resolved.

## 1.0.0

**Nov 13, 2017**

### Minimum Mule Version

**4.0.0**

## See Also

- [JSON Threat Protection for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-json-threat-protection)

- [Known Issues](https://help.salesforce.com/s/issues)