Urgent.News

What's breaking now, across thousands of outlets.

Tech

Java4Shell segue sem correção no Debian estável; sid já tem o patch

Debian estável ainda usa builds afetados Em 19 de novembro de 2026, os pacotes OpenJDK dos repositórios de segurança do Debian 12 e 13 continuavam na faixa vulnerável à Java4Shell, identificada como CVE-2026-114938. A correção estava disponível no sid, a distribuição instável, mas ainda não havia chegado aos pacotes estáveis; por isso, uma atualização comum pelo apt não resolvia o problema. Os…

Original Portuguese Read in English

Debian 12 and 13 still use affected builds of the OpenJDK packages from Debian's security repositories at the time of November 19, 2026. The fix was available in sid, the unstable distribution, but had not yet reached stable packages. Common apt updates did not resolve the issue. The Debian 12 builds were openjdk-17 17.0.21+9-1~deb12u1, while Debian 13 had openjdk-21 21.0.13+9-1~deb13u2 and openjdk-25 25.0.5+8-1~deb13u1.

The security tracker marked the three as vulnerable with no DSA. In sid, the fixed builds listed were 17.0.21.1+2-1, 21.0.13.1+2-1, and 25.0.5.1+2-1. Upstream versions for the fixed builds were 17.0.21.1, 21.0.13.1, and 25.0.5.1 or later. The forky still had affected builds at 21.0.13.0.3+1-1 and 25.0.5+8-1 during testing. The required version depends on the distribution, with bookworm using Java 17 and trixie offering the 21 and 25 lines.

Confirm hardware, packages, and Java processes, as the failure only triggers the vulnerable path on x86-64 processors exposing the four instruction flags simultaneously. ARM64 and x86 machines without AVX-512 VBMI are not affected. Verify the host using the command: grep -oE (avx512f|avx512bw|avx512vbmi|bmi2) /proc/cpuinfo | sort -u.

Check installed packages and candidate versions. For Debian 13, look at the 21 and 25 lines; for Debian 12, check the 17 line. Applications like Elasticsearch and Jira installers may include a separate JVM, so the Java in PATH does not necessarily represent all host processes. Compare the runtime version with the Base64 intrinsic flag using apt-cache policy.

The flag is enabled by default in the affected builds; check the JVM used, not just the configuration or Java invoked in a different session. Use the commands java -version and java -XX:+PrintFlagsFinal -version 2 /dev/null | grep UseBASE64Intrinsics to confirm the JVM in use. Disable the intrinsic in services by starting each JVM with -XX:-UseBASE64Intrinsics.

This can be done by setting JAVA_TOOL_OPTIONS in /etc/environment for login sessions, but not for systemd-managed services, which typically do not start in a PAM session. Configure the variable in a drop-in unit for each systemd service. If it already defines JAVA_TOOL_OPTIONS, combine the values, as a later declaration overrides an earlier one.

Use the service demoapp as an example, adapting the service name and confirming the flag in the active JVM after reloading systemd and restarting the unit. The service must report UseBASE64Intrinsics = false. Repeat the procedure for each Java service and validate the process after the reboot; jcmd is part of the JDK, so the JDK package may need to be installed on hosts with only the JRE.

Install a patched Temurin build from the Adoptium apt repository as another alternative. The provided example configures the keyring and repository entry using the system codename without replacing the distribution commands. Update the index and confirm that the patched Java 17 build is the candidate before installing. For Debian 13, choose the package used by the services, temurin-21-jdk or temurin-25-jdk, and confirm the corresponding candidate version.

Update-alternatives can be used to set java to the patched build, and systemd services can be restarted to use the new runtime.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at dev.to →

More in Tech

Ubuntu PHP packages remain vulnerable to CVE-2026-115560 and CVE-2026-129289 flaws

Two upstream-fixed flaws still affected Ubuntu packages The PHP project fixed CVE-2026-115560, tied to a session serializer incompatibility, and CVE-2026-129289, an ambiguous request flaw in PHP-FPM…

  • Ubuntu continues to be vulnerable to two PHP package vulnerabilities despite upstream fixes.
  • CVE-2026-115560 and CVE-2026-129289 were corrected on November 19, 2026.
  • Canonical assigned a 9.2 score and critical severity to the flaws, but priority is marked as medium.

38 Free Dev Tools That Run Entirely in Your Browser

I build small tools for the jobs I keep doing by hand — converting a stylesheet, typing out an interface from a JSON response, checking a regex before it goes into production.

  • 38 developer tools operate entirely in browser
  • Tools cover format conversion, APIs, AI, testing
  • Privacy ensured as no server stores pasted data

Content-Addressable Memory vs SRAM Search: Asking Memory to Do the Matching

Most memory answers one question: given an address, return the value stored there. A network switch or a router asks the opposite question: given a value — a destination IP, a MAC address — which…

  • Content-addressable memory (CAM) quickly matches inputs against stored entries in parallel.
  • Static random-access memory (SRAM) requires sequential scans or hashing to find matches.
  • CAM offers instant response but consumes more power and space than SRAM.

More from Friday 20 November →