Skip to content

Fix Chrome advisory parser for 2026+ blog post format #39

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
jasinner merged 1 commit into from
Jul 6, 2026
Merged

Fix Chrome advisory parser for 2026+ blog post format #39

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
5 changes: 4 additions & 1 deletion advisory_parser/parsers/chrome.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,10 @@ def parse_chrome_advisory(url):

# Workaround for advisories that do not use <div>s for each CVE entry. E.g.:
# https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
advisory_text = re.sub(r"(.)\[", r"\1\n[", advisory_text)
advisory_text = re.sub(r"(.)\[\$", r"\1\n[$", advisory_text)
# 2026+ posts concatenate CVE entries on one line using [TBD][bugid],
# [N/A][bugid], or [$reward][bugid]. Split them into separate lines.
advisory_text = re.sub(r"(?<=\S)(\[(?:TBD|N/A|\$\d+)\]\[)", r"\n\1", advisory_text)

if SECURITY_FIXES_HEADER not in advisory_text:
raise AdvisoryParserTextException("No security fixes found in {}".format(url))
Expand Down
Loading