Skip to content

Add CVE-2025-58767: DoS vulnerability in REXML#3617

Merged
hsbt merged 1 commit into
ruby:masterfrom
naitoh:rexml-cve-2025-58767
Sep 17, 2025
Merged

Add CVE-2025-58767: DoS vulnerability in REXML#3617
hsbt merged 1 commit into
ruby:masterfrom
naitoh:rexml-cve-2025-58767

Conversation

@naitoh

@naitoh naitoh commented Sep 17, 2025

Copy link
Copy Markdown
Contributor

No description provided.

@naitoh
naitoh requested a review from a team as a code owner September 17, 2025 06:06
@naitoh
naitoh force-pushed the rexml-cve-2025-58767 branch from 2336487 to 54a7cd4 Compare September 17, 2025 06:09

@kou kou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

+1

@mame @hsbt Could you merge this?

@hsbt hsbt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks always 👍

@hsbt
hsbt merged commit b933697 into ruby:master Sep 17, 2025
1 check passed
@naitoh
naitoh deleted the rexml-cve-2025-58767 branch September 17, 2025 06:31
@kou

kou commented Sep 17, 2025

Copy link
Copy Markdown
Member

Ah, sorry... This article wasn't published because the date uses a future date:

https://github.com/ruby/www.ruby-lang.org/actions/runs/17788666874/job/50560893546#step:5:13

          Skipping: en/news/_posts/2025-09-18-dos-rexml-cve-2025-58767.md has a future date

@hsbt Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

@hsbt

hsbt commented Sep 17, 2025

Copy link
Copy Markdown
Member

or simply modified publish data like 2025-09-17T6:00:00+09:00? I'm okay to re-run at today's night.

@kou

kou commented Sep 17, 2025

Copy link
Copy Markdown
Member

@naitoh Which approach do you prefer?

@naitoh

naitoh commented Sep 17, 2025

Copy link
Copy Markdown
Contributor Author

@hsbt @kou

Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

Please, this.

@hsbt

hsbt commented Sep 17, 2025

Copy link
Copy Markdown
Member

The publish date is 2025-09-18 03:00:00 +0000. It means this advisory will publish 9/18 12:00 JST. I'm not sure that time is intentional. But I will re-run that after 12:00 JST today.

@kou

kou commented Sep 18, 2025

Copy link
Copy Markdown
Member

Yes. The publish date isn't strictly correct. We just don't care about strict date.

FYI: We can merge any other PR such as #3623 instead of re-run the job to publish this article.

@hsbt

hsbt commented Sep 18, 2025

Copy link
Copy Markdown
Member

@kou

kou commented Sep 18, 2025

Copy link
Copy Markdown
Member

Thanks!

1 similar comment
@naitoh

naitoh commented Sep 18, 2025

Copy link
Copy Markdown
Contributor Author

Thanks!

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