admin: Update security alerts and clarify security policy#5232
Merged
lgritz merged 1 commit intoJun 14, 2026
Merged
admin: Update security alerts and clarify security policy#5232lgritz merged 1 commit into
lgritz merged 1 commit into
Conversation
Also make our CONTRIBUTING guide link to, and be consistent with, our SECURITY.md policy file. Follow OpenEXR's lead by explaining briefly that we only consider something to be a security issue if it can plausibly be triggered by ordinary inputs coming from untrusted parties. For example, a maliciously crafted input image may be a vulnerability, but incorrect use of an API call is not, because only trusted parties should have direct access to the APIs. Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Jun 14, 2026
…twareFoundation#5232) Also make our CONTRIBUTING guide link to, and be consistent with, our SECURITY.md policy file. Follow OpenEXR's lead by explaining briefly that we only consider something to be a security issue if it can plausibly be triggered by ordinary inputs coming from untrusted parties. For example, a maliciously crafted input image may be a vulnerability, but incorrect use of an API call is not, because only trusted parties should have direct access to the APIs. Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Jun 15, 2026
…twareFoundation#5232) Also make our CONTRIBUTING guide link to, and be consistent with, our SECURITY.md policy file. Follow OpenEXR's lead by explaining briefly that we only consider something to be a security issue if it can plausibly be triggered by ordinary inputs coming from untrusted parties. For example, a maliciously crafted input image may be a vulnerability, but incorrect use of an API call is not, because only trusted parties should have direct access to the APIs. Signed-off-by: Larry Gritz <lg@larrygritz.com>
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 free
to 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.
Also make our CONTRIBUTING guide link to, and be consistent with,
our SECURITY.md policy file.
Follow OpenEXR's lead by explaining briefly that we only consider
something to be a security issue if it can plausibly be triggered by
ordinary inputs coming from untrusted parties. For example, a
maliciously crafted input image may be a vulnerability, but incorrect
use of an API call is not, because only trusted parties should have
direct access to the APIs.