CVE-2026-46439 oscal-compass CVE debrief

Who should care

Defenders managing compliance-trestle deployments, especially those rendering untrusted input in templates, should assess exposure and apply patches or mitigations as available. Defenders should prioritize verifying exposure in compliance-trestle deployments, especially where untrusted input is rendered in templates, and apply patches or mitigations as available. This includes operators, platform administrators, vulnerability management teams, and security

Why it matters

CVE-2026-46439 is a Server-Side Template Injection (SSTI) vulnerability in compliance-trestle that allows for arbitrary command execution. Defenders should prioritize verifying exposure and applying patches or mitigations.

• Potential for arbitrary command execution with privileges of the running process
• Need for verification of exposure in compliance-trestle deployments
• Priority for applying patches or mitigations
• Importance of monitoring for suspicious activity in compliance-trestle environments

Technical summary

The `trestle author jinja` command in compliance-trestle recursively evaluates rendered templates, allowing an attacker to achieve arbitrary command execution with privileges of the running process by injecting malicious payloads into data fields. This vulnerability is caused by recursive re-compilation and re-rendering of already-rendered output. Defenders should prioritize verifying exposure in compliance-trestle deployments, especially where untrusted input is rendered in templates, and apply patches or mitigations as available. The vulnerability does not require attacker control of the template itself.

Defensive priority

Defenders should prioritize verifying exposure in compliance-trestle deployments, especially where untrusted input is rendered in templates, and apply patches or mitigations as available.

Recommended defensive actions

• Verify compliance-trestle deployments for exposure to untrusted input in templates
• Apply patches or mitigations as available
• Monitor for suspicious activity in compliance-trestle environments
• 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, affected versions, and patched versions. However, specific details about exploitation or victim impact are not provided. Defenders should verify exposure in compliance-trestle deployments, especially where untrusted input is rendered in templates, and apply patches or mitigations as available. The vulnerability exists in the `trestle author jinja` command and allows for arbitrary command execution with privileges of the running process by injecting malicious payloads 3

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.