4 hours ago
fastjson

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.checkAutoTypeTypeUtils.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>
14 hours ago
selenium

Nightly

Commits

  • 66f1b48: [build] Automated Browser Version Update (#17828) (Selenium CI Bot) #17828
  • a9f2bc5: [py] Include generated files in API docs published on Read the Docs (#17794) (Corey Goldberg) #17794
  • 0293446: [py] Fix docs build for RtD (#17830) (Corey Goldberg) #17830
  • 3760c6c: [py] Revert RtD doc build changes (#17831) (Corey Goldberg) #17831
  • 9fd65b5: [build] BiDi schema generation cleanup (#17837) (Titus Fortner) #17837
1 days ago
logback

Logback 1.6.1

2026-07-28 Release of logback version 1.6.1

• In TimeBasedRollingPolicy, when the file option is set, the intermediate file renamed before asynchronous compression now receives the target archive name without the compression suffix (e.g. .gz, .zip, .xz). Previously it used a nanotime-based .tmp suffix. This makes the file easier to identify if compression fails during rollover. (See also the following paragraph.)

• On GZ, ZIP, or XZ compression failure, the original (uncompressed) log file is no longer deleted. Compression strategies now delete the source file only after successful compression and emit a warning that the original was left intact.

• ConsoleAppender with now probes JLine's org.jline.jansi.AnsiConsole first and falls back to the legacy FuseSource org.fusesource.jansi.AnsiConsole class. This keeps ANSI coloring working after Jansi moved under the JLine project. The optional org.jline:jansi-core artifact is declared as a dependency alongside the existing FuseSource jansi dependency. A preferredJansiClassName property was added for tests. This issue was reported in issues/1043 by seonwoo_jung who also provided the relevant PR.

• LayoutWrappingEncoder now reports an error at start() when no layout is set and guards encode() against a null layout. Previously, a missing layout (for example after an ignored // branch) allowed the encoder to start and then fail with a NullPointerException on every event, resulting in silent log loss. This issue was reported in issues/1046 by seonwoo_jung who also provided the relevant PR.

• FileCollisionAnalyser now detects file collisions involving nested appenders of SiftingAppender. When the nested file or fileNamePattern does not textually reference the discriminator key (e.g. ${userId}), a warning is issued at configuration time naming the appender, the key, and the shared target. This closes a gap where statically declared file appenders were checked but sifted nested appenders were not. This enhancement was contributed in PR #1041 by seonwoo_jung.

• More defensive handling in SyslogOutputStream and SyslogAppenderBase: the close() method now ensures that resources are closed, writes and flushes check that the underlying resources are in a valid state and fallback to no-op otherwise.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 57759f433000a133088ef0441038963134437fbd associated with the tag v_1.6.1. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

• See https://logback.qos.ch/news.html#1.6.1 for the original text.

1 days ago
Activiti
1 days ago
Activiti