Standard change template with special characters (^) is not saved

Templates that contain ^ in one of the field values do not work.

Steps to reproduce demonightlyhelsinki and demonightlyistanbul , demonightlylondon
Create change template:
1) In a field (for example, Test Plan), add: crontab -l|grep -v "^#"
2) Fill in a Category (mandatory field).
3) Click "Request Approval"
4) When click Save or Request Approval, a field is automatically added "Active is true". I removed it.
5) Approve it in Related Link at bottom.
6) Then create a standard change with the template that was just created

Special characters are not there. It is truncated to: -l|grep -v "

On some customer's instances, they try to create a change from a standard template with special characters, and the page just blanks out.

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided not to address this issue. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support. The reason for this is 

"This is a limitation of how values are stored in template fields. We need a character to differentiate conditions in what is stored in the DB as a plain text string, and we've always used carrots (^) for this in our filter code. Changing this would be extremely high risk (as it would impact our basic filter and queries in addition to templates), and we would just need to use a different character that would still end up triggering this behavior.