Improper Handling of Case Sensitivity Affecting flux-operator package, versions <0.43.0-r1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-WOLFILATEST-FLUXOPERATOR-15385271
- published4 Mar 2026
- disclosed26 Feb 2026
Introduced: 26 Feb 2026
CVE-2026-27896 (opens in a new tab)How to fix?
Upgrade Wolfi flux-operator to version 0.43.0-r1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream flux-operator package and not the flux-operator package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
The Go MCP SDK used Go's standard encoding/json.Unmarshal for JSON-RPC and MCP protocol message parsing in versions prior to 1.3.1. Go's standard library performs case-insensitive matching of JSON keys to struct field tags — a field tagged json:"method" would also match "Method", "METHOD", etc. This violated the JSON-RPC 2.0 specification, which defines exact field names. A malicious MCP peer may have been able to send protocol messages with non-standard field casing that the SDK would silently accept. This had the potential for bypassing intermediary inspection and coss-implementation inconsistency. Go's standard JSON unmarshaling was replaced with a case-sensitive decoder in commit 7b8d81c. Users are advised to update to v1.3.1 to resolve this issue.