[
https://issues.apache.org/jira/browse/HADOOP-19690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020434#comment-18020434
]
ASF GitHub Bot commented on HADOOP-19690:
-----------------------------------------
pjfanning opened a new pull request, #7970:
URL: https://github.com/apache/hadoop/pull/7970
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
CVE-2025-48924
See https://issues.apache.org/jira/browse/HADOOP-19690 for reason to upgrade
commons-text too.
### How was this patch tested?
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Bump commons-lang3 to 3.18.0 due to CVE-2025-48924
> --------------------------------------------------
>
> Key: HADOOP-19690
> URL: https://issues.apache.org/jira/browse/HADOOP-19690
> Project: Hadoop Common
> Issue Type: Task
> Reporter: PJ Fanning
> Priority: Major
>
> https://www.cve.org/CVERecord?id=CVE-2025-48924
> Will update commons-text to 1.14.0 which was released with commons-lang3
> 3.18.0. Due to https://issues.apache.org/jira/browse/HADOOP-19532 - seems
> best to upgrade them together.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
