---
schema_version: "1"
id: 7d28057f83c4f173bbb73ccb347d064dd7812cc044b24c57be9f2cbb5b8d3a6b
title: JSON Threat Protection
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/policies/json-threat-protection-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/policies/json-threat-protection-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: bd7195fd8ea3c6e548d8b24bfa3da46a2e1bb3868678ebc4204786381d2b4cc6
description: MuleSoft Documentation Site
latest: true
---
# JSON Threat Protection

## [](#1-2-2)1.2.2

**October 1, 2026**

### What’s New

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

## [](#1-2-0)1.2.0

**March 15, 2023**

### [](#minimum-mule-version)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)1.1.5

**Jun 1, 2022**

### [](#minimum-mule-version-2)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues)Fixed issues

- Policy considered valid a payload containing multiple JSON objects.

## [](#1-1-4)1.1.4

**Apr 30, 2020**

### [](#minimum-mule-version-3)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements)New Features and Enhancements

- Performance improvements are introduced to the header manipulation engine.

### [](#fixed-issues-2)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)1.1.3

**Jul 24, 2019**

### [](#minimum-mule-version-4)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-2)New Features and Enhancements

Several performance improvements are introduced in this release.

### [](#fixed-issues-3)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)1.1.2

**Apr 26, 2019**

### [](#minimum-mule-version-5)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-3)New Features and Enhancements

Several performance improvements are introduced in this release.

## [](#1-1-1)1.1.1

**Jun 25, 2018**

### [](#minimum-mule-version-6)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-4)New Features and Enhancements

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

## [](#1-1-0)1.1.0

**Jan 25, 2018**

### [](#minimum-mule-version-7)Minimum Mule Version

**4.1.0**

### [](#new-features-and-enhancements-5)New Features and Enhancements

Reduced error-handling verbosity in templates.

### [](#fixed-issues-4)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)1.0.0

**Nov 13, 2017**

### [](#minimum-mule-version-8)Minimum Mule Version

**4.0.0**

## [](#see-also)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)