Skip to content

Conversation

@bagder
Copy link
Member

@bagder bagder commented Jan 2, 2026

we reject the idea of CRLF injection by the user itself as a general security problem

we reject the idea of *CRLF injection* as a security problem
@bagder bagder marked this pull request as ready for review January 2, 2026 09:55
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new section to the vulnerability disclosure policy documenting curl's stance on CRLF injection, clarifying that the ability to send carriage-return (CR) and line-feed (LF) characters is an intentional feature rather than a security vulnerability.

  • Adds a "CRLF in data" section explaining curl's policy on handling CRLF sequences
  • Explicitly states that CRLF injection is not considered a security problem
  • Clarifies that users have control over what data they send through curl

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Viktor Szakats <vszakats@users.noreply.github.com>
@bagder bagder closed this in ae1597c Jan 2, 2026
@bagder bagder deleted the bagder/crlf branch January 2, 2026 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants