Skip to content

tags: add more unicode security references #1074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
robUx4 merged 1 commit into from
Feb 25, 2026
Merged

tags: add more unicode security references #1074

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cellar-tags/tags_security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Tag values can be either `TagString` or `TagBinary` blobs. In both cases issues

Most of the time strings are kept as-is and don't pose a security issue, apart from invalid UTF-8 values.
Implementations **MUST** validate `TagString` inputs for UTF-8 correctness and
reasonable length before use, in accordance with the security considerations in [@!RFC3629, section 10].
reasonable length before use, in accordance with the security considerations in [@!RFC3629, section 10] and [@!RFC9839, section 7].

String tags that are parsed (such as "REPLAYGAIN_GAIN" or "REPLAYGAIN_PEAK" defined in (#technical-information)),
string tags following the TagString formatting rules (#tagstring-formatting), or string tags following other strict formats like URLs,
Expand Down