PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-86318 java-json-tools CVE debrief

A flaw in java-json-tools json-patch up to 1.13 can lead to a stack-based buffer overflow when executing a manipulation via JsonMergePatch.fromJson in JsonMergePatchDeserializer.java. The attack may be performed remotely. The exploit has been published and may be used. However, the project was informed early but has not responded yet. The vulnerability affects systems using java-json-tools json-patch, particularly those exposed to remote attacks. Defenders should assess their exposure and verify the affected versions in their inventory.

Vendor
java-json-tools
Product
json-patch
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-07
Original CVE updated
2026-09-07
Advisory published
2026-09-07
Advisory updated
2026-09-07

Who should care

Defenders responsible for systems using java-json-tools json-patch, especially those exposed to remote attacks, should assess their exposure and verify the affected versions in their inventory.

Why it matters

Defenders should prioritize verifying the affected versions and assessing exposure in their inventory, especially in systems where remote attacks are a concern, due to the published exploit and unknown remediation status.

  • Verify affected versions in inventory
  • Assess exposure in remote attack scenarios
  • Monitor for exploitation attempts

Technical summary

The JsonMergePatch.fromJson function in JsonMergePatchDeserializer.java of java-json-tools json-patch up to 1.13 is vulnerable to a stack-based buffer overflow. This can be exploited remotely by manipulating the input. The vulnerability affects systems using java-json-tools json-patch, particularly those exposed to remote attacks. Defenders should prioritize verifying the affected versions and assessing exposure in their inventory, especially in systems where remote attacks are a concern, due to the published exploit and unknown remediation status.

Defensive priority

Defenders should prioritize verifying the affected versions and assessing exposure in their inventory, especially in systems where remote attacks are a concern.

Recommended defensive actions

  • Verify the affected versions of java-json-tools json-patch in your inventory
  • Assess exposure in systems where remote attacks are a concern
  • Monitor for exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the vendor's response and remediation status are unknown. The vulnerability has been publicly disclosed and an exploit has been published. Defenders should verify the affected versions of java-json-tools json-patch in their inventory and assess exposure in systems where remote attacks are a concern.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-86318 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-86318

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-86318 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-86318

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.