Skip to content

Conversation

@jedisct1
Copy link

@jedisct1 jedisct1 commented Jan 26, 2026

Change summary

VCL content currently allows control characters, which are stored without modification.

This allows injecting control characters that manipulate the user’s terminal, potentially causing the CLI to display VCL code different from the code being executed.

Fix this by escaping control sequences.

This is a low-impact issue, as it requires write access to the VCL.

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

  • Does your submission pass tests?

Changes to Core Features:

  • Have you written new tests for your core changes, as applicable?
  • Have you successfully run tests with your changes locally?

User Impact

Escape sequences are now displayed as escaped.

Are there any considerations that need to be addressed for release?

@jedisct1 jedisct1 requested a review from a team as a code owner January 26, 2026 22:45
VCL content currently allows control characters, which are stored
without modification.

This allows a malicious API token owner to inject control characters
that manipulate the user’s terminal, potentially causing the CLI to
display VCL code different from the code being executed.

Fix this by escaping control sequences.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant