Skip to content

all: use case-sensitive JSON unmarshaling - #807

Merged
maciej-kisiel merged 2 commits into
mainfrom
mkisiel/json-unmarshal
Feb 18, 2026
Merged

maciej-kisiel merged 2 commits into
mainfrom
mkisiel/json-unmarshal

Conversation

@maciej-kisiel

Copy link
Copy Markdown
Contributor

As reported in #805, case insensitive unmarshaling can pose security issues. This change adjusts all non-test and non-example unmarshaling to use a case sensitive mode.

This introduces a new external dependency github.com/segmentio/encoding.

@maciej-kisiel

Copy link
Copy Markdown
Contributor Author

@findleyr I'll leave it up go give you an opportunity for review, since you already engaged in the topic. I plan to merge it tomorrow morning (EMEA) at the latest and will likely release v1.3.1 with it as well.

@findleyr findleyr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Amazing! Thanks for being so on top of this.

@maciej-kisiel
maciej-kisiel merged commit 7b8d81c into main Feb 18, 2026
9 checks passed
maciej-kisiel added a commit that referenced this pull request Feb 18, 2026
As reported in
#805, case
insensitive unmarshaling can pose security issues. This change adjusts
all non-test and non-example unmarshaling to use a case sensitive mode.

This introduces a new external dependency
`github.com/segmentio/encoding`.
@maciej-kisiel
maciej-kisiel deleted the mkisiel/json-unmarshal branch February 20, 2026 14:53
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.

3 participants