CVE-2026-112249 grandnode CVE debrief

Who should care

Defenders responsible for grandnode grandnode2 deployments should assess exposure and prioritize upgrading to version 2.4.0-beta or 2.4.0. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify if their current version is affected and take appropriate actions to mitigate this vulnerability.

Why it matters

Defenders should prioritize upgrading to version 2.4.0-beta or 2.4.0 and apply the patch to address this cross-site scripting vulnerability, as it can be exploited remotely and compromise user interactions.

• Cross-site scripting attacks can be launched remotely, potentially leading to unauthorized actions on the affected system.
• Successful exploitation could result in the injection of malicious scripts, compromising user interactions with the grandnode grandnode2 application.
• Defenders should verify if their current version is affected and prioritize upgrading to mitigate this vulnerability.
• Inventory checks and monitoring for suspicious activity related to the Product Description Handler are recommended.

Technical summary

The vulnerability is located in the Html.Raw function of the Product.Description Handler in grandnode grandnode2 up to version 2.3.0. This allows for cross-site scripting attacks, which can be launched remotely. The manipulation results in cross site scripting. Upgrading to version 2.4.0-beta and 2.4.0 is able to address this issue. The patch is identified as 41a8e349eab8d9641cf6ea800d738f2d8991ca22. Defenders should prioritize upgrading to version 2.4.0-beta or 2.4.0 and apply the patch to address this cross-site scripting vulnerability.

Defensive priority

Defenders should prioritize upgrading to version 2.4.0-beta or 2.4.0 and apply the patch 41a8e349eab8d9641cf6ea800d738f2d8991ca22 to address this cross-site scripting vulnerability.

Recommended defensive actions

• Upgrade to version 2.4.0-beta or 2.4.0
• Apply the patch 41a8e349eab8d9641cf6ea800d738f2d8991ca22
• Review and update the Product Description Handler
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description, affected versions, and patch information. Defenders should verify if their current version is affected and prioritize upgrading to mitigate this vulnerability. The patch 41a8e349eab8d9641cf6ea800d738f2d8991ca22 is identified as a fix for this issue. Evidence from the CVE Program and NVD supports this assessment.

Sources and 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.