chore(deps): bump the other-security group across 5 directories with 3 updates

[dependabot]

Bumps the other-security group with 1 update in the /hugegraph-store/hg-store-core directory: com.alibaba:fastjson.
Bumps the other-security group with 1 update in the /hugegraph-store/hg-store-rocksdb directory: com.alibaba:fastjson.
Bumps the other-security group with 1 update in the /hugegraph-pd/hg-pd-cli directory: org.yaml:snakeyaml.
Bumps the other-security group with 1 update in the /hugegraph-struct directory: com.google.guava:guava.
Bumps the other-security group with 1 update in the /hugegraph-pd/hg-pd-client directory: org.yaml:snakeyaml.

Updates com.alibaba:fastjson from 1.2.83 to 1.2.84

Release notes

Sourced from com.alibaba:fastjson's releases.

fastjson 1.2.84版本发布

fastjson 1.2.84 Release Notes

Release Date: 29 Jul 2026 Tag: 1.2.84 (72553ed)

Security fix release, backporting the fastjson2 AutoType hardening to the 1.2.x line. All users parsing untrusted JSON are strongly recommended to upgrade.

Security Fixes

1. Reject type names containing URL-special characters (:/!) in ParserConfig.checkAutoType and TypeUtils.loadClass, so a non-class-name string never reaches the class loader
2. Verify the accept name text after a whitelist hash match, so a hash collision alone cannot whitelist a type name
3. An accept prefix no longer covers ClassLoader/DataSource/RowSet gadget base types; only an accept entry naming the type in full is an explicit opt-in
4. Fixed deny classes being cached by loadClass before the blacklist check, so a repeated checkAutoType call could return a blacklisted class from the cache

Maven Dependency Configuration

<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>fastjson</artifactId>
    <version>1.2.84</version>
</dependency>

概述

安全修复版本，将 fastjson2 的 AutoType 加固回移到 1.2.x 版本线。强烈建议所有解析不可信 JSON 的用户升级。

安全修复

1. 在 ParserConfig.checkAutoType 和 TypeUtils.loadClass 中拒绝包含 URL 特殊字符（:/!）的类型名，非类名字符串不再可能到达类加载器
2. 白名单 hash 命中后增加 accept 名称文本回验，仅 hash 碰撞无法再绕过白名单
3. accept 前缀不再覆盖 ClassLoader/DataSource/RowSet 等危险基类；只有完整类名的 accept 条目才视为显式放行
4. 修复危险类在黑名单检查前被 loadClass 缓存的问题：此前重复调用 checkAutoType 可能从缓存中直接返回黑名单类

Maven 依赖配置

<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>fastjson</artifactId>
    <version>1.2.84</version>
</dependency>

Commits

• 72553ed build: disable javadoc doclint for modern JDK builds
• 6ac7847 1.2.84 release: add central-publishing plugin, bump version
• 73675f6 build: restore junit test dependency (as in 1.2.84 init)
• ad353ff fix: strengthen autoType type name validation and whitelist verification
• See full diff in compare view

Updates com.alibaba:fastjson from 1.2.83 to 1.2.84

Release notes

Sourced from com.alibaba:fastjson's releases.

fastjson 1.2.84版本发布

fastjson 1.2.84 Release Notes

Release Date: 29 Jul 2026 Tag: 1.2.84 (72553ed)

Security fix release, backporting the fastjson2 AutoType hardening to the 1.2.x line. All users parsing untrusted JSON are strongly recommended to upgrade.

Security Fixes

1. Reject type names containing URL-special characters (:/!) in ParserConfig.checkAutoType and TypeUtils.loadClass, so a non-class-name string never reaches the class loader
2. Verify the accept name text after a whitelist hash match, so a hash collision alone cannot whitelist a type name
3. An accept prefix no longer covers ClassLoader/DataSource/RowSet gadget base types; only an accept entry naming the type in full is an explicit opt-in
4. Fixed deny classes being cached by loadClass before the blacklist check, so a repeated checkAutoType call could return a blacklisted class from the cache

Maven Dependency Configuration

<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>fastjson</artifactId>
    <version>1.2.84</version>
</dependency>

概述

安全修复版本，将 fastjson2 的 AutoType 加固回移到 1.2.x 版本线。强烈建议所有解析不可信 JSON 的用户升级。

安全修复

1. 在 ParserConfig.checkAutoType 和 TypeUtils.loadClass 中拒绝包含 URL 特殊字符（:/!）的类型名，非类名字符串不再可能到达类加载器
2. 白名单 hash 命中后增加 accept 名称文本回验，仅 hash 碰撞无法再绕过白名单
3. accept 前缀不再覆盖 ClassLoader/DataSource/RowSet 等危险基类；只有完整类名的 accept 条目才视为显式放行
4. 修复危险类在黑名单检查前被 loadClass 缓存的问题：此前重复调用 checkAutoType 可能从缓存中直接返回黑名单类

Maven 依赖配置

<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>fastjson</artifactId>
    <version>1.2.84</version>
</dependency>

Commits

• 72553ed build: disable javadoc doclint for modern JDK builds
• 6ac7847 1.2.84 release: add central-publishing plugin, bump version
• 73675f6 build: restore junit test dependency (as in 1.2.84 init)
• ad353ff fix: strengthen autoType type name validation and whitelist verification
• See full diff in compare view

Updates org.yaml:snakeyaml from 1.33 to 2.0

Commits

• c98ffba issue 561: add negative test case
• e2ca740 Use Maven wrapper on github
• 49d91a1 Fix target for github
• 19e331d Disable toolchain for github
• 42c7812 Cobertura plugin does not work
• 03c82b5 Rename GlobalTagRejectionTest to be run by Maven
• 6e8cd89 Remove cobertura
• d9b0f48 Improve Javadoc
• 519791a Run install and site goals under docker
• 82f33d2 Merge branch 'master' into add-module-info
• Additional commits viewable in compare view

Updates com.google.guava:guava from 25.1-jre to 32.0.0-jre

Release notes

Sourced from com.google.guava:guava's releases.

32.0.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>32.0.0-jre</version>
  <!-- or, for Android: -->
  <version>32.0.0-android</version>
</dependency>

Jar files

• 32.0.0-jre.jar
• 32.0.0-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 32.0.0-jre
• 32.0.0-android

JDiff

• 32.0.0-jre vs. 31.1-jre
• 32.0.0-android vs. 31.1-android
• 32.0.0-android vs. 32.0.0-jre

Changelog

Security fixes

• Reimplemented Files.createTempDir and FileBackedOutputStream to further address CVE-2020-8908 (#4011) and CVE-2023-2976 (#2575). (feb83a1c8f)

While CVE-2020-8908 was officially closed when we deprecated Files.createTempDir in Guava 30.0, we've heard from users that even recent versions of Guava have been listed as vulnerable in other databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used FileBackedOutputStream class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under "Incompatible changes" below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to 32.0.1 which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we warn that common.io in particular may not work under Windows, we didn't intend to regress support.) Sorry for the trouble.

Incompatible changes

Although this release bumps Guava's major version number, it makes no binary-incompatible changes to the guava artifact.

One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:

• The new implementations of Files.createTempDir and FileBackedOutputStream throw an exception under Windows. This is fixed in 32.0.1. Sorry for the trouble.
• guava-gwt now requires GWT 2.10.0.
• This release makes a binary-incompatible change to a @Beta API in the separate artifact guava-testlib. Specifically, we changed the return type of TestingExecutors.sameThreadScheduledExecutor to ListeningScheduledExecutorService. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)

... (truncated)

Commits

• See full diff in compare view

Updates org.yaml:snakeyaml from 1.28 to 2.0

Commits

• c98ffba issue 561: add negative test case
• e2ca740 Use Maven wrapper on github
• 49d91a1 Fix target for github
• 19e331d Disable toolchain for github
• 42c7812 Cobertura plugin does not work
• 03c82b5 Rename GlobalTagRejectionTest to be run by Maven
• 6e8cd89 Remove cobertura
• d9b0f48 Improve Javadoc
• 519791a Run install and site goals under docker
• 82f33d2 Merge branch 'master' into add-module-info
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.