CVE-2026-114361 HarnessRouter CVE debrief

Who should care

Defenders responsible for HarnessRouter instances, especially those with Identity Mode enabled, should assess exposure and prioritize upgrading to version 0.31.11 if vulnerable. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, plan updates or mitigations, and monitor for potential exploitation attempts.

Why it matters

Defenders should prioritize verifying exposure of HarnessRouter instances, especially those with Identity Mode enabled, and upgrade to version 0.31.11 if vulnerable.

• Verify exposure of HarnessRouter instances
• Upgrade to version 0.31.11 if vulnerable
• Monitor for potential exploitation attempts

Technical summary

The vulnerability affects an unknown function of the file gateway/app.py of the component Identity Mode in HarnessRouter up to 0.31.10. Performing a manipulation of the argument X-Harness-Org/X-Harness-Member results in improper authorization. The attack is possible to be carried out remotely with high complexity and difficult exploitability. Upgrading to version 0.31.11 mitigates this issue. Defenders should prioritize verifying exposure of HarnessRouter instances, especially those with Identity Mode enabled, and upgrade to version 0.31.11 if vulnerable.

Defensive priority

Defenders should prioritize verifying exposure of HarnessRouter instances, especially those with Identity Mode enabled, and upgrade to version 0.31.11 if vulnerable.

Recommended defensive actions

• Verify exposure of HarnessRouter instances, especially those with Identity Mode enabled
• Upgrade to version 0.31.11 if vulnerable
• Monitor for potential 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 vulnerability was detected in HarnessRouter up to 0.31.10 and can be mitigated by upgrading to version 0.31.11. The attack is possible to be carried out remotely with high complexity and difficult exploitability. Evidence is limited to public sources and CVE metadata. Defenders should verify exposure and upgrade if vulnerable, monitoring for potential exploitation attempts.

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.