Uh oh!
There was an error while loading. Please reload this page.
OTP27 support - allow_entities - #7
Merged
Merged
Conversation
up2jj
self-requested a review
October 27, 2025 07:19
up2jj
approved these changes
Oct 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A change in xmerl defaults released in OTP 27, and made in erlang/otp#7539 (c.f. detailed release notes)
Some default values in Xmerl has been changed to avoid XML External Entity
(XXE) vulnerabilities if you're parsing untrusted XML.
xmerl_scan: the default value for allow_entities has changed to false.
xmerl_sax_parser: the default value for external_entities has changed to none.
Own Id: OTP-19079
Application(s): xmerl
Related Id(s): GH-7539
XXE was not discovered in OTP26 so it's safe to use these entities for OTP27