SShortSingh.
Back to feed

Debian stable still ships Java builds affected by CVE-2026-114938 while the fix sits in sid

0
·3 views

As of November 19, 2026, OpenJDK packages in Debian 12 and 13 security repositories remained in the version range vulnerable to the Java4Shell flaw, tracked as CVE-2026-114938. Corrected builds were available in the unstable distribution sid but had not yet reached the stable packages, so a routine apt upgrade would not fix the issue. The vulnerable path is only triggered on x86-64 processors exposing four specific instruction flags, while ARM64 systems and x86 machines without AVX-512 VBMI fall outside the described scope. Administrators are advised to check their CPU flags, compare installed runtime versions against the fixed releases, and consider mitigations such as disabling the Base64 intrinsic via JVM options or installing patched Temurin builds from the Adoptium repository.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Local RAG system lets lab researchers query notes and slides with traceable citations

A research team built a local retrieval-augmented generation service that answers questions about their lab's Markdown notes and PowerPoint slides. Gemma 4 31B generates text descriptions of rendered slides so that figure content becomes searchable, while Qwen3-Embedding-4B embeds both source text and those descriptions into a Qdrant index. Answers are produced by DeepSeek-V4.1-Flash-1017 from up to four retrieved excerpts, and the service lists every supplied excerpt with its file path and line or slide number. In a November 2026 test over 143 files, both sample questions in Japanese and English returned the expected path with a supporting citation. The author notes that valid citation IDs only locate passages, so a person must still verify that each passage supports the claim it is cited for.

0
ProgrammingDEV Community ·

WebAssembly and Containers Offer Different Approaches to Isolating Untrusted Code

Running code a developer did not write, such as plugins, serverless functions, and third-party dependencies, is a persistent challenge that containers have traditionally addressed. Containers isolate processes using Linux kernel namespaces, cgroups, and seccomp, giving each one a near-normal userspace while sharing the host kernel. WebAssembly instead runs portable bytecode in a sandboxed virtual machine that has no system access unless the host explicitly grants capabilities. The article notes Wasm starts in microseconds to low milliseconds, compared with tens to hundreds of milliseconds for containers, which benefits short-lived, high-frequency functions. In exchange, Wasm requires compilation to its format and offers a narrower set of host capabilities, while containers support nearly any Linux binary.

0
ProgrammingDEV Community ·

Most high-traffic pages in an AI tool directory still show templated text

A developer reviewing a directory of 4,323 AI tools found that 130 of the 150 most-visited listings still contain only auto-generated boilerplate rather than written descriptions. Those templated pages account for about 64% of reads among the top 150, while the 20 hand-written pages make up the rest. For example, the most-read unrewritten page, Muse Wonder, reduces to three sentences that cite only a price label, a category, a rank, and a tag. Many of these listings were claimed by their vendors, yet their pages still lack any real product description. The author concludes that the directory's most popular free-tool listings often contain no meaningful text at all.

0
ProgrammingDEV Community ·

Team-wide AI adoption depends more on shared workflows and tools than on the model

The author, who has tested many AI approaches at work, found that getting one person to use AI effectively is easy, while getting a whole team to use it daily is harder. The main obstacles are not the models themselves but the mindset and whether tools fit how teams already operate. The piece argues that adoption spreads when work happens in shared channels where colleagues can see prompts, results, and corrections. It recommends letting AI handle repeatable chores while people make the key decisions, turning proven experiments into deterministic scripts or checks, and designing tools that fit existing chat, thread, and document habits.