Skip to content

Pre-release updates. #1124

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
davidlehn merged 2 commits into from
Nov 25, 2025
Merged

Pre-release updates. #1124

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e17e0be
Run new security test.
davidlehn Nov 25, 2025
bb489b9
Fix typos.
davidlehn Nov 25, 2025
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
14 changes: 7 additions & 7 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ Forge ChangeLog

## 1.3.1 - 2022-03-29

### Fixes
### Fixed
- RFC 3447 and RFC 8017 allow for optional `DigestAlgorithm` `NULL` parameters
for `sha*` algorithms and require `NULL` paramters for `md2` and `md5`
for `sha*` algorithms and require `NULL` parameters for `md2` and `md5`
algorithms.

## 1.3.0 - 2022-03-17
Expand Down Expand Up @@ -164,11 +164,11 @@ Forge ChangeLog
and is being removed rather than fixed.
- **SECURITY**, **BREAKING**: Remove `forge.util.parseUrl()` (and
`forge.http.parseUrl` alias) and use the [WHATWG URL
Standard](https://url.spec.whatwg.org/). `URL` is supported by modern browers
and modern Node.js. This change is needed to address URL parsing security
issues. If `forge.util.parseUrl()` is used directly or through `forge.xhr` or
`forge.http` APIs, and support is needed for environments without `URL`
support, then a polyfill must be used.
Standard](https://url.spec.whatwg.org/). `URL` is supported by modern
browsers and modern Node.js. This change is needed to address URL parsing
security issues. If `forge.util.parseUrl()` is used directly or through
`forge.xhr` or `forge.http` APIs, and support is needed for environments
without `URL` support, then a polyfill must be used.
- **BREAKING**: Remove `forge.task` API. This API was never used, documented,
or advertised by the maintainers. If anyone was using this API and wishes to
continue development it in other project, please let the maintainers know.
Expand Down
1 change: 1 addition & 0 deletions tests/security/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
// tests related to security, vulnerability reports, etc
require('./cve-2025-12816.js');
require('./ghsa-554w-wpv2-vw27.js');