Repository navigation
Correct Ghost embed-preview advisory references - #10319
Open
eprogressing wants to merge 1 commit into
Open
eprogressing wants to merge 1 commit into
eprogressing wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
eprogressing/advisory-improvement-10319
October 12, 2026 07:59
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
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.
The Ghost embed-card XSS record currently references Penpot GHSA-qvq5-c536-pmx8, an unrelated chunk-upload temporary-storage amplification advisory. Remove that reference and add the two upstream commits implementing the Ghost fix:
security.embedPreviewUrlset tohttps://public.ghostembeds.com/.Both commits appear in the v6.65.0...v6.67.0 comparison, matching the Ghost advisory's patched version and configuration guidance. The Penpot advisory concerns a different product and vulnerability.
Validation: one advisory, references only; OSV schema and format validation and whitespace checks pass. Version ranges, severity, description and attribution remain unchanged. This is a public metadata correction based on source and release verification, not a claim of discovering or runtime-reproducing the vulnerability.