# out-of-memory

Published articles for out-of-memory.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Crashing Microcontrollers Competitively

DevFeed: [Crashing Microcontrollers Competitively](<https://devfeed.tech/articles/crashing-microcontrollers-competitively-145841.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/19/crashing-microcontrollers-competitively/>)

Author: Zoe Skyforest

Published: 2026-11-20T06:00:17Z

Content type: news

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [browser-game](<https://devfeed.tech/topics/browser-game.md>)

Tags: [arduino](<https://devfeed.tech/tags/arduino.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [crash](<https://devfeed.tech/tags/crash.md>), [esp](<https://devfeed.tech/tags/esp.md>), [esp32](<https://devfeed.tech/tags/esp32.md>), [esp32-p4](<https://devfeed.tech/tags/esp32-p4.md>), [esp8266](<https://devfeed.tech/tags/esp8266.md>), [game](<https://devfeed.tech/tags/game.md>), [load](<https://devfeed.tech/tags/load.md>), [memory](<https://devfeed.tech/tags/memory.md>), [microcontroller](<https://devfeed.tech/tags/microcontroller.md>), [microcontrollers](<https://devfeed.tech/tags/microcontrollers.md>), [misc-hacks](<https://devfeed.tech/tags/misc-hacks.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pi-pico](<https://devfeed.tech/tags/pi-pico.md>), [pico](<https://devfeed.tech/tags/pico.md>), [raspberry](<https://devfeed.tech/tags/raspberry.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [stm8](<https://devfeed.tech/tags/stm8.md>), [toilet](<https://devfeed.tech/tags/toilet.md>)

### AI overview

Kacken Open Air is a browser game where players compete for festival toilets by knocking on their doors. Each in-game toilet is paired with a real ESP8266: knocks add computational load, eventually slowing it enough to eject its occupant, and continued knocking can exhaust memory and crash it, collapsing the toilet in the game. The setup uses a cluster that includes an ESP32-P4, ESP8266s, Raspberry Pi Pico 2s, Arduino Dues, and an STM8 as a hardware watchdog. The excerpt describes the concept and components but does not provide implementation details or performance measurements.

### Source excerpt

[Ani] has produced rather an interesting game. Kacken Open Air (KOA) is a browser-based game, wherein players compete for access to a limited resource--namely, festival toilets. So far, so amusing, ...read more

## Help prevent out-of-memory restarts on Aurora MySQL 8.4

DevFeed: [Help prevent out-of-memory restarts on Aurora MySQL 8.4](<https://devfeed.tech/articles/help-prevent-out-of-memory-restarts-on-aurora-mysql-8-4-129584.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/help-prevent-out-of-memory-restarts-on-aurora-mysql-8-4/>)

Author: Aayushi Mittal

Published: 2026-11-11T16:51:16Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [memory handling](<https://devfeed.tech/topics/memory-handling.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [2](<https://devfeed.tech/tags/2.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [control](<https://devfeed.tech/tags/control.md>), [event](<https://devfeed.tech/tags/event.md>), [help](<https://devfeed.tech/tags/help.md>), [learn](<https://devfeed.tech/tags/learn.md>), [management](<https://devfeed.tech/tags/management.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [memory-pressure](<https://devfeed.tech/tags/memory-pressure.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [oom](<https://devfeed.tech/tags/oom.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [protection](<https://devfeed.tech/tags/protection.md>), [take](<https://devfeed.tech/tags/take.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Aurora MySQL 8.4 enables automatic memory management by default to respond to memory pressure before the operating system kills `mysqld` and restarts the cluster. The article shows how to monitor `AuroraMemoryHealthState`, recovery status and CloudWatch counters, then use error logs and Performance Schema to identify whether connection buffers, temporary tables or another consumer is driving pressure. In its test, Aurora shed work with query declines and connection terminations while keeping the database up; disabling protection led to an OOM restart. The article recommends keeping automatic management on for most 8.4 workloads and alerting on sustained memory-health values above zero. Manual control requires explicitly setting `aurora_oom_response` on 8.4, where it is empty by default when automatic management is off; some actions have pairing or deployment limits. Serverless v2 scales capacity before terminating connections and does not support `tune` or `tune_buffer_pool`. Applications should handle error 1041.

### Source excerpt

Out-of-memory restarts drop every connection and force an Aurora MySQL cluster restart. Learn how Aurora MySQL 8.4's automatic memory management prevents them: confirm protection is active, read the signals during a memory-pressure event, monitor OOM avoidance with CloudWatch, and decide when to take manual control.

## What Memory Management Can Teach Us About Debt, Fiat Money, and Sustainability

DevFeed: [What Memory Management Can Teach Us About Debt, Fiat Money, and Sustainability](<https://devfeed.tech/articles/what-memory-management-can-teach-us-about-debt-fiat-money-and-sustainability-128460.md>)

Original publisher: [Read original article](<https://hackernoon.com/what-memory-management-can-teach-us-about-debt-fiat-money-and-sustainability?source=rss>)

Author: DoubleX

Published: 2026-11-11T07:29:53Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [memory handling](<https://devfeed.tech/topics/memory-handling.md>), [Finance](<https://devfeed.tech/topics/finance.md>), [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>), [arc memory management](<https://devfeed.tech/topics/arc-memory-management.md>)

Tags: [1-4](<https://devfeed.tech/tags/1-4.md>), [2](<https://devfeed.tech/tags/2.md>), [2-2](<https://devfeed.tech/tags/2-2.md>), [2020](<https://devfeed.tech/tags/2020.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [can](<https://devfeed.tech/tags/can.md>), [desktop-ssd](<https://devfeed.tech/tags/desktop-ssd.md>), [economics](<https://devfeed.tech/tags/economics.md>), [fiat](<https://devfeed.tech/tags/fiat.md>), [garbage-collection](<https://devfeed.tech/tags/garbage-collection.md>), [management](<https://devfeed.tech/tags/management.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-leak](<https://devfeed.tech/tags/memory-leak.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [money](<https://devfeed.tech/tags/money.md>), [oom-killer](<https://devfeed.tech/tags/oom-killer.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [programming](<https://devfeed.tech/tags/programming.md>), [promises](<https://devfeed.tech/tags/promises.md>), [resource](<https://devfeed.tech/tags/resource.md>), [resource-management](<https://devfeed.tech/tags/resource-management.md>), [sustainability](<https://devfeed.tech/tags/sustainability.md>), [swapspace](<https://devfeed.tech/tags/swapspace.md>)

### AI overview

The article uses memory management as an analogy for debt, fiat money, and ecological limits. It explains programming risks such as circular-reference leaks, allocation failures, and heavy use of swap, then likens borrowing against future memory to finance that depends on future production and resource extraction. It argues that compound debt growth pressures demand and resource use, while supply-chain dependence can spread failures. Its numerical estimates and forecasts are presented as rough calculations based on figures attributed to AI, not as established measurements. The author proposes anchoring ordinary money to a disclosed basket of electricity, essential goods, services, and precious metals, with fiat money reserved for emergencies and subject to legislative and judicial review. The proposal remains oversimplified; the article acknowledges risks including corruption, security concerns, international coordination, and political abuse.

### Source excerpt

Memory management in programming is surprisingly similar to natural resource management in economics :)

## TapeSAC: Automated, Pareto-Optimal Fine-Grained Memory Management for Large Model Training

DevFeed: [TapeSAC: Automated, Pareto-Optimal Fine-Grained Memory Management for Large Model Training](<https://devfeed.tech/articles/tapesac-automated-pareto-optimal-fine-grained-memory-management-for-large-model-training-116500.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.04897>)

Author: Kaihui Ren, Yifan Zhao, Zejian Wang, Yingtong Xiong, Xiaoling Zhou, Daohong Xu, Chenhao Guan, Zhikang Mo, Jihu Guo, Zhuoru Ma, Yufeng Li, Lin Zhang, Yiqiao Liao, Chengru Song

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [LLM Techniques](<https://devfeed.tech/topics/llm-techniques.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [activation](<https://devfeed.tech/tags/activation.md>), [automated](<https://devfeed.tech/tags/automated.md>), [batch](<https://devfeed.tech/tags/batch.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [kernels](<https://devfeed.tech/tags/kernels.md>), [large](<https://devfeed.tech/tags/large.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [model-training](<https://devfeed.tech/tags/model-training.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [planner](<https://devfeed.tech/tags/planner.md>), [planning](<https://devfeed.tech/tags/planning.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [qwen3](<https://devfeed.tech/tags/qwen3.md>), [qwen3-5](<https://devfeed.tech/tags/qwen3-5.md>), [qwen3-6](<https://devfeed.tech/tags/qwen3-6.md>), [qwen3-8](<https://devfeed.tech/tags/qwen3-8.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

TapeSAC automates selective activation checkpointing in eager PyTorch without changes to model forward code. It records block operations at the dispatcher and, during backward, replays only producers of values autograd consumes; a planner chooses tensors to save using measured recomputation costs under a step-peak memory limit. On Qwen3.8-27B and Qwen3.6-35B-A3B, replay alone cut step time by 3.0% and 1.7% versus full checkpointing at no greater memory cost; memory-aware planning improved those gains to 6.3% and 13.9% with a 90%-of-device-memory limit. The evaluated hand-tuned policies fell short of the reported frontier, and one ran out of memory at larger batches. Across 500 real-data steps, TapeSAC reduced training time by 8-11%; on Qwen3.5-397B it was 2.7% faster than a model-specific hand-tuned policy while using 14% less memory.

### Source excerpt

arXiv:2611.04897v1 Announce Type: new Abstract: Selective activation checkpointing (SAC) decides which activations to save for the backward pass and which to recompute: each choice is a point in the plane of peak memory and recomputation time, and the goal is that plane's Pareto frontier. Current practice falls short of this goal. Hand-tuned policies fix a single point that does not adapt when the model, batch or kernels change; PyTorch's SAC reruns each block's forward pass in program order, recomputing values the backward pass never reads; and the memory budget of torch.compile treats recomputation as free or forbidden and selects saved tensors by bytes alone, an assumption that fails for the custom kernels that produce many of a large model's activations. We present TapeSAC, which automates SAC in eager PyTorch without editing the model's forward code. TapeSAC records each block's forward pass at the dispatcher and, during backward, replays only the producers of the values autograd consumes, so saving a tensor eliminates every producer needed only for it. A planner selects the saved tensors from measured recomputation costs under a single limit on step-peak memory. On Qwen3.8-27B and Qwen3.6-35B-A3B, replay alone reduces step time by 3.0% and 1.7% versus full checkpointing at no greater memory cost; memory-aware planning raises these gains to 6.3% and 13.9% under a 90%-of-device-memory limit. The evaluated hand-tuned policies fall short of this memory-recomputation frontier and, on Qwen3.6-35B-A3B, run out of memory at larger batches. Over 500 steps on real data, TapeSAC reduces training time by 8-11%; on Qwen3.5-397B, it is 2.7% faster than a model-specific hand-tuned policy while using 14% less memory.

## Replacing the newsroom with one workflow | 💻Gerard Klijs🦀

DevFeed: [Replacing the newsroom with one workflow | 💻Gerard Klijs🦀](<https://devfeed.tech/articles/replacing-the-newsroom-with-one-workflow-gerard-klijs-109210.md>)

Original publisher: [Read original article](<https://swamp-club.com/feed/p/b16a82d3-c672-4d88-85c8-6664757726e7/go>)

Author: gklijs

Published: 2026-10-30T07:39:31Z

Content type: article

Language: en

Sources: [Swamp Club Feed](<https://devfeed.tech/sources/swamp-club-feed.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Image](<https://devfeed.tech/topics/image.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [conference](<https://devfeed.tech/tags/conference.md>), [diffusion](<https://devfeed.tech/tags/diffusion.md>), [digest](<https://devfeed.tech/tags/digest.md>), [event](<https://devfeed.tech/tags/event.md>), [event-sourcing](<https://devfeed.tech/tags/event-sourcing.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [illustration](<https://devfeed.tech/tags/illustration.md>), [local-model](<https://devfeed.tech/tags/local-model.md>), [memory](<https://devfeed.tech/tags/memory.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [model](<https://devfeed.tech/tags/model.md>), [news](<https://devfeed.tech/tags/news.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [repo](<https://devfeed.tech/tags/repo.md>), [swamp](<https://devfeed.tech/tags/swamp.md>), [video](<https://devfeed.tech/tags/video.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

The author describes a one-person newsroom workflow that runs twice each weekday: one run covers neurodiversity and the other basic income. Each takes a couple of minutes to gather news and social posts, summarize them with a local model, email a digest, draft a LinkedIn post, and generate an illustration with Stable Diffusion XL. Both topics use the same workflow. The author switched from qwen3.6:35b-a3b, which ran out of memory, to the lighter qwen3:14b. They attribute the workflow's event-sourcing approach to keeping a record of each run, with changes added as new layers rather than silently replacing prior state. The excerpt does not provide further technical details.

### Source excerpt

Yesterday at the AxonIQ conference I learned about brag, a Claude Code skill that turns a repository into a short launch video. So today I pointed it at my own repo, and it made a 20-second pitch deck out of a swamp workflow. The workflow is my one-person newsroom. Every weekday afternoon it runs...

## When Log Parsing Removes What Matters: Detecting Failures in Distributed GPU Workloads

DevFeed: [When Log Parsing Removes What Matters: Detecting Failures in Distributed GPU Workloads](<https://devfeed.tech/articles/when-log-parsing-removes-what-matters-detecting-failures-in-distributed-gpu-workloads-107356.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.14009>)

Author: Boyuan Cui, Yuyang Zeng, Yifang Tian, Hans-Arno Jacobsen

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Multi-GPU](<https://devfeed.tech/topics/multi-gpu.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [bench](<https://devfeed.tech/tags/bench.md>), [communication](<https://devfeed.tech/tags/communication.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [cuda](<https://devfeed.tech/tags/cuda.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [detection](<https://devfeed.tech/tags/detection.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [execution](<https://devfeed.tech/tags/execution.md>), [failure](<https://devfeed.tech/tags/failure.md>), [fault-injection](<https://devfeed.tech/tags/fault-injection.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [llm](<https://devfeed.tech/tags/llm.md>), [logs](<https://devfeed.tech/tags/logs.md>), [multi-gpu](<https://devfeed.tech/tags/multi-gpu.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [parsing](<https://devfeed.tech/tags/parsing.md>)

### AI overview

GF-Bench is a PyTorch framework and dataset for evaluating failure detection in distributed GPU workloads. Its current release contains 220 labeled two-GPU runs covering normal behavior, CUDA out-of-memory fail-stop faults, and persistent-straggler fail-slow faults. On parsed logs, DeepLog, LogAnomaly, LogBERT, and LogPrompt with in-context learning or chain-of-thought prompting did not reliably detect both fault classes; the highest overall F1 was 0.667. For LogPrompt, using raw logs raised ICL's overall F1 to 0.983, but required 9.0 times the average input tokens and 8.9 times the per-run cost. The results suggest parsing can lower token use and inference cost while discarding execution context needed for accurate detection. The framework is designed to extend to other workloads and fault types.

### Source excerpt

arXiv:2610.14009v2 Announce Type: replace-cross Abstract: Large AI models increasingly rely on distributed GPU execution, yet it remains unclear whether established anomaly detection methods transfer effectively to this setting. We introduce GF-Bench, a PyTorch-based framework for generating controlled failures in distributed GPU workloads, and a dataset produced with it. The framework supports extensible workload and fault-injection logic; based on this design, the current release targets failures visible in multi-GPU communication logs and provides 220 labeled two-GPU runs covering normal behavior, CUDA out-of-memory fail-stop faults, and persistent-straggler fail-slow faults. Using GF-Bench, we evaluate three sequence-based methods (DeepLog, LogAnomaly, and LogBERT) and the large language model (LLM)-based LogPrompt with in-context learning (ICL) and chain-of-thought (CoT) prompting strategies on parsed logs, and additionally evaluate LogPrompt on raw logs. On parsed inputs, no method reliably detects both failure classes, and the highest overall F1 score is 0.667. Raw inputs raise the overall F1 score of ICL-LogPrompt to 0.983, at 9.0x its average input-token usage and 8.9x its per-run cost. These results reveal a trade-off between effectiveness and efficiency: parsed inputs reduce LLM token use and inference cost but can discard the distributed execution context required for accurate failure detection. GF-Bench provides a reproducible basis for studying cost-efficient anomaly detection methods and can be extended to additional GPU workloads and failure types.

## php2shell one week later: Why one exploit doesn't work everywhere

DevFeed: [php2shell one week later: Why one exploit doesn't work everywhere](<https://devfeed.tech/articles/php2shell-one-week-later-why-one-exploit-doesn-t-work-everywhere-107160.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/php2shell-one-week-later-why-one-exploit-doesnt-work-everywhere>)

Author: Joshua Martinelle, Thomas Cappetta

Published: 2026-10-30T01:42:06Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [CVE-2021-44228](<https://devfeed.tech/topics/cve-2021-44228.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>)

Tags: [appliances](<https://devfeed.tech/tags/appliances.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [honeypots](<https://devfeed.tech/tags/honeypots.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [internet](<https://devfeed.tech/tags/internet.md>), [memory-handling](<https://devfeed.tech/tags/memory-handling.md>), [network-appliances](<https://devfeed.tech/tags/network-appliances.md>), [online](<https://devfeed.tech/tags/online.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [scanning](<https://devfeed.tech/tags/scanning.md>)

### AI overview

Tenable's week of testing found that php2shell can enable remote code execution, but exploitation generally requires tuning to the target's PHP build, SAPI, extensions, and runtime configuration. Five exposed vulnerable sites saw exploitation attempts but no compromise; successful execution was reported on researcher honeypots and network appliances. Public probes can misclassify systems: version matches do not prove exploitability, and stateful checks may miss vulnerable hosts or flag patched ones. Checks also depend on memory limits and worker reuse, and can crash workers. Shared-build appliances are a key exception because one tuned exploit may reach many devices. Prioritize patching or isolating internet-facing management interfaces, network appliances, and end-of-life PHP systems; use vendor fixes for appliances. Update PHP to fixed releases or distribution packages, and apply mitigations while upgrading legacy branches.

### Source excerpt

php2shell raised fears of mass exploitation. A week of testing by our research team found that working exploits had to be fitted to each target's exact PHP setup. Systems that share one build, such as network appliances, are the exception: one tuned exploit can reach every device that runs it. Key takeaways The five vulnerable PHP sites we exposed to the internet were not compromised, and public proofs-of-concept (PoCs) that go beyond version checks do not reliably confirm whether a host is vulnerable. Exploitation has been confirmed elsewhere, on researcher honeypots and on some network appliances. In realistic environments, turning php2shell into remote code execution usually takes an exploit built for the specific target. That is hard, not impossible, and it puts php2shell in a different category from Log4Shell, even though both received near-maximum severity ratings. Where many systems share one build, such as network appliances, a single calibrated exploit can work against all of them. Patch now, starting with internet-facing management interfaces, network appliances, and end-of-life PHP branches. Tenable Nessus and Tenable One Web App Scanning have had version-based detection since October 21. Background On October 20, 2026, PHP announced two vulnerabilities, and on October 21 released fixes for flaws that can allow unauthenticated remote code execution. CVE-2026-109618 is an out-of-memory handling flaw. CVE-2026-109619 is a use-after-free flaw caused by stale state shared between requests on the same worker. Each has a CVSSv4 score of 9.2. For a full breakdown of affected versions, fixes and mitigations, see our frequently asked questions blog post. This post covers what happened after the disclosure, based on what our team observed directly. From disclosure to headline in under 48 hours php2shell got big fast. Details of the vulnerabilities leaked online before the official release. Within two days, the vulnerability had a name, a logo and coverage in mainst

## GTFormer: A Syntax-Free Graph Network Alternative to Transformers for 8192$\\times$ Length Extrapolation in Linear Time

DevFeed: [GTFormer: A Syntax-Free Graph Network Alternative to Transformers for 8192$\\times$ Length Extrapolation in Linear Time](<https://devfeed.tech/articles/gtformer-a-syntax-free-graph-network-alternative-to-transformers-for-8192-times-length-extrapolation-in-linear-time-104098.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.37524>)

Author: Elisabeth Fink

Published: 2026-10-28T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Neural Network](<https://devfeed.tech/topics/neural-network.md>), [Transformer](<https://devfeed.tech/topics/transformer.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [attention](<https://devfeed.tech/tags/attention.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [gnn](<https://devfeed.tech/tags/gnn.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [graph](<https://devfeed.tech/tags/graph.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [linear](<https://devfeed.tech/tags/linear.md>), [long-context](<https://devfeed.tech/tags/long-context.md>), [memory](<https://devfeed.tech/tags/memory.md>), [modeling](<https://devfeed.tech/tags/modeling.md>), [natural-language-processing](<https://devfeed.tech/tags/natural-language-processing.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [random](<https://devfeed.tech/tags/random.md>), [raw](<https://devfeed.tech/tags/raw.md>), [reduction](<https://devfeed.tech/tags/reduction.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [sequence](<https://devfeed.tech/tags/sequence.md>), [syntax](<https://devfeed.tech/tags/syntax.md>), [transformers](<https://devfeed.tech/tags/transformers.md>)

### AI overview

GTFormer replaces flat self-attention with a syntax-free hierarchical graph network designed for linear-time, long-context sequence modeling. It combines a balanced binary reduction tree, boundary-bridging shift edges, random expander shortcuts, convex highway gating and a top-down broadcast pass. The abstract reports tests on eight code, log and multi-hop retrieval benchmarks, with training limited to sequences of at most 512 tokens. It claims zero-shot extrapolation to 4,194,304 tokens (8192x) on one commodity GPU with linear memory and near-perfect accuracy, while standard and RoPE Transformers encounter attention collapse or memory exhaustion. These are abstract-reported results; the supplied evidence does not include methods or benchmark details to assess them further.

### Source excerpt

arXiv:2610.37524v1 Announce Type: new Abstract: Self-attention mechanisms have established the Transformer as the dominant backbone across natural language processing, source code intelligence, and automated theorem proving. However, all-to-all pairwise token comparison enforces a quadratic $\mathcal{O}(N^2)$ compute and memory barrier alongside severe softmax attention dilution as sequence length $N$ scales beyond the training horizon. Inspired by recent advances in algebraic graph learning (\textbf{WPNet}), this work introduces \textbf{GTFormer}, a syntax-free hierarchical Graph Neural Network (GNN) that replaces flat self-attention for general long-context sequence modeling. GTFormer organizes raw token streams into a bounded-degree hierarchy combining a balanced binary reduction tree ($\lceil \log_2 N \rceil$ depth), horizontal boundary-bridging shift edges, random expander shortcuts, multi-channel convex highway gating, and a top-down broadcast pass. Across eight long-context code, log, and multi-hop retrieval benchmarks trained exclusively on sequences of length $N \le 512$, GTFormer extrapolates zero-shot to $N = 4{,}194{,}304$ ($8192\times$) on a single commodity GPU in linear $\mathcal{O}(N)$ memory, maintaining near-perfect accuracy where standard and RoPE Transformers suffer from out-of-distribution attention collapse and out-of-memory exhaustion.

## PHP2Shell exposes the weakness in coordinated vulnerability disclosure

DevFeed: [PHP2Shell exposes the weakness in coordinated vulnerability disclosure](<https://devfeed.tech/articles/php2shell-exposes-the-weakness-in-coordinated-vulnerability-disclosure-96467.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4239342/php2shell-exposes-the-weakness-in-coordinated-vulnerability-disclosure.html>)

Author: Taryn Plumb

Published: 2026-10-23T00:39:33Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [calif](<https://devfeed.tech/tags/calif.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [coordinated-vulnerability-disclosure](<https://devfeed.tech/tags/coordinated-vulnerability-disclosure.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [deep-research](<https://devfeed.tech/tags/deep-research.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [government](<https://devfeed.tech/tags/government.md>), [it](<https://devfeed.tech/tags/it.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [oom](<https://devfeed.tech/tags/oom.md>), [openai](<https://devfeed.tech/tags/openai.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [php](<https://devfeed.tech/tags/php.md>), [php-programming-languages-security-software-development-vulnerabilities](<https://devfeed.tech/tags/php-programming-languages-security-software-development-vulnerabilities.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [programming-languages](<https://devfeed.tech/tags/programming-languages.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>)

### AI overview

The PHP2Shell disclosure shows how early patch access can shorten defenders' response window: after the PHP project advanced its release amid circulating CVE IDs and a PoC video, Chainguard published fixed images about six hours before the revised release time. The PHP Foundation said this exposed a fix attackers could study; Chainguard said it acted on evidence of active exploitation and information already circulating. AWS and Cloudflare reported exploit attempts before public disclosure, though AWS said the source of the early information was unclear. The excerpt argues coordinated disclosure remains useful but is difficult to protect as more parties receive patches and AI tools can help analyze flaws. Suggested preparations include tracking software and dependencies with an SBOM, knowing where runtimes are deployed, deciding in advance who can take services offline, and detecting unusual process execution or new web server files because CVE signatures may not exist on day zero.

### Source excerpt

Two critical vulnerabilities discovered in the widely-used PHP programming language have shaken up enterprises, and the ramifications will take some time to truly understand. But one of the lesser-known stories centers around disclosure. According to The PHP Foundation, several organizations had agreed to a coordinated release detailing the critical flaws and mitigation actions, but cybersecurity firm Chainguard "unlaterally" broke this embargo. This prompted the PHP project to release its patches early, but also allowed attackers to study the fix in binary form and craft proofs-of-concept (PoCs) for exploits before defenders had a chance to update their systems. But some, including AWS and Cloudflare, contend that active exploits began hours, even days before the disclosure. By some estimates, there have since been millions of attempts to abuse the 9.2-severity-rated bugs, collectively known as PHP2Shell. Many organizations, including government bodies, have reacted by taking their websites offline altogether. "Frankly, the disclosure story is more interesting than the bugs themselves," said Frank Dickson of Dickson Research. "Embargoes matter. This one was nearly impossible to keep." The messy disclosure CVE-2026-109618 and CVE-2026-109619 could allow attackers to launch remote code execution (RCE) attacks. The PHP Foundation acknowledged that one of its contractors had discovered the first signs of the out-of-memory (OOM) problem behind CVE-2026-109618 as far back as 2024, but "no concrete vectors" were found, and other issues with "clear impact" overshadowed its concerns about the flaw. Deep research into the problem didn't occur until July 30, 2026, after the Foundation got the PHP project into OpenAI's Patch the Planet program. Researchers from Calif, OpenAI, and Google Cloud's Wiz "made the full impact of the OOM problem clear," and fixing it became top priority. Once researchers developed patches, distributors, including Chainguard, received them in advance

## New Serious PHP Vulnerabilities Released and Patched

DevFeed: [New Serious PHP Vulnerabilities Released and Patched](<https://devfeed.tech/articles/new-serious-php-vulnerabilities-released-and-patched-95808.md>)

Original publisher: [Read original article](<https://www.schneier.com/blog/archives/2026/10/new-serious-php-vulnerabilities-released-and-patched.html>)

Author: Bruce Schneier

Published: 2026-10-22T13:26:51Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>), [Schneier on Security](<https://devfeed.tech/sources/schneier-on-security.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [PHP](<https://devfeed.tech/topics/php.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [memory](<https://devfeed.tech/tags/memory.md>), [mod-php](<https://devfeed.tech/tags/mod-php.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [patched](<https://devfeed.tech/tags/patched.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php](<https://devfeed.tech/tags/php.md>), [php-fpm](<https://devfeed.tech/tags/php-fpm.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [web](<https://devfeed.tech/tags/web.md>), [worker](<https://devfeed.tech/tags/worker.md>)

### AI overview

PHP releases 8.5.12, 8.4.27, 8.3.36, and 8.2.35 patch two critical flaws that can enable unauthenticated remote code execution. The excerpt identifies all PHP installations serving web requests as at risk, including PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, and LiteSpeed; it describes mod_php as highest risk because an unauthenticated request can trigger the demonstrated attack before application code runs. One flaw involves request cleanup treating partially initialized data as valid after out-of-memory handling; the other involves a later request reusing freed request state in the same worker before initialization resets it. The text says updating PHP is the only way to regain security.

### Source excerpt

PHP maintainers have released fixes for two critical vulnerabilities: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution. All PHP users are strongly encouraged to update immediately. Who is at risk: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs...

## 5 Commands to Protect Critical Apps From the Linux OOM Killer

DevFeed: [5 Commands to Protect Critical Apps From the Linux OOM Killer](<https://devfeed.tech/articles/5-commands-to-protect-critical-apps-from-the-linux-oom-killer-95340.md>)

Original publisher: [Read original article](<https://www.tecmint.com/stop-oom-killer-killing-apps/>)

Author: Ravi Saive

Published: 2026-10-22T09:49:33Z

Content type: tutorial

Language: en

Sources: [Tecmint: Linux Howtos, Tutorials & Guides](<https://devfeed.tech/sources/tecmint-linux-howtos-tutorials-guides.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [cgroups](<https://devfeed.tech/topics/cgroups.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>)

Tags: [almalinux](<https://devfeed.tech/tags/almalinux.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [apt](<https://devfeed.tech/tags/apt.md>), [btrfs](<https://devfeed.tech/tags/btrfs.md>), [cat](<https://devfeed.tech/tags/cat.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [chmod](<https://devfeed.tech/tags/chmod.md>), [commands](<https://devfeed.tech/tags/commands.md>), [conf](<https://devfeed.tech/tags/conf.md>), [database](<https://devfeed.tech/tags/database.md>), [debian](<https://devfeed.tech/tags/debian.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-commands](<https://devfeed.tech/tags/linux-commands.md>), [linux-oom-killer](<https://devfeed.tech/tags/linux-oom-killer.md>), [memory](<https://devfeed.tech/tags/memory.md>), [oom](<https://devfeed.tech/tags/oom.md>), [oom-score-adj](<https://devfeed.tech/tags/oom-score-adj.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [process](<https://devfeed.tech/tags/process.md>), [systemd-memorymax](<https://devfeed.tech/tags/systemd-memorymax.md>)

### AI overview

The excerpt presents five ways to manage Linux out-of-memory events: inspect kernel logs and process OOM scores; adjust a running process with `choom` or persist its priority through systemd's `OOMScoreAdjust`; limit a service with cgroups v2 `MemoryHigh` and `MemoryMax`; add swap for short memory spikes; and use `systemd-oomd` to respond to sustained memory pressure. It distinguishes temporary process adjustments from persistent service settings, and explains that cgroup limits confine OOM kills to the affected service. Full immunity with `OOMScoreAdjust=-1000` can leave the kernel with no killable process and cause a system panic. The excerpt notes platform limits: Btrfs needs a specially created swap file, and Rocky Linux/RHEL may require enabling PSI before `systemd-oomd` can monitor pressure. Swap buys time but does not fix leaks; ongoing OOM events still call for addressing the cause or adding memory.

### Source excerpt

The post 5 Commands to Protect Critical Apps From the Linux OOM Killer first appeared on Tecmint: Linux Howtos, Tutorials & Guides . Your database keeps disappearing overnight, and the only clue is a kernel line saying "Out of memory: Killed process". Here's The post 5 Commands to Protect Critical Apps From the Linux OOM Killer first appeared on Tecmint: Linux Howtos, Tutorials & Guides.

## The Phantom OOM: How a Silent Session Leak Brought Down Our Microservice Every 48 Hours

DevFeed: [The Phantom OOM: How a Silent Session Leak Brought Down Our Microservice Every 48 Hours](<https://devfeed.tech/articles/the-phantom-oom-how-a-silent-session-leak-brought-down-our-microservice-every-48-hours-93933.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-phantom-oom-how-a-silent-session-leak-brought-down-our-microservice-every-48-hours?source=rss>)

Author: Himashi Meththasena

Published: 2026-10-21T20:51:24Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Cloud Native Operations](<https://devfeed.tech/topics/cloud-native-operations.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [background](<https://devfeed.tech/tags/background.md>), [coding](<https://devfeed.tech/tags/coding.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [container](<https://devfeed.tech/tags/container.md>), [crash](<https://devfeed.tech/tags/crash.md>), [database](<https://devfeed.tech/tags/database.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [devops](<https://devfeed.tech/tags/devops.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [leak](<https://devfeed.tech/tags/leak.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-leak](<https://devfeed.tech/tags/memory-leak.md>), [microservice-architecture](<https://devfeed.tech/tags/microservice-architecture.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [oom](<https://devfeed.tech/tags/oom.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [phantom-oom](<https://devfeed.tech/tags/phantom-oom.md>), [python](<https://devfeed.tech/tags/python.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

A FastAPI service's memory rose steadily until Kubernetes killed its pod; increasing its memory limit only lengthened the crash cycle. The team traced the pattern to long-lived or unmanaged SQLAlchemy sessions in background tasks: exception and timeout paths skipped cleanup, while PostgreSQL showed idle connections and the gap between opened and closed sessions widened. They replaced manual session handling with a context manager that commits on success, rolls back on exceptions, and always closes the session, and set engine pool size, overflow, recycling, and pre-ping options. The excerpt reports memory stabilizing at 350 MB, no OOM exits for months, and 70% fewer active database connections after deployment.

### Source excerpt

If you've ever chased a phantom memory leak in a microservice architecture, you know how frustrating it is.

## Security advisories: CVE-2026-80212 and CVE-2026-80213

DevFeed: [Security advisories: CVE-2026-80212 and CVE-2026-80213](<https://devfeed.tech/articles/security-advisories-cve-2026-80212-and-cve-2026-80213-19157.md>)

Original publisher: [Read original article](<https://www.ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv/>)

Published: 2026-08-27T00:00:00Z

Content type: news

Language: en

Sources: [Ruby-lang](<https://devfeed.tech/sources/ruby-lang.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [bypass](<https://devfeed.tech/tags/bypass.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dns](<https://devfeed.tech/tags/dns.md>), [library](<https://devfeed.tech/tags/library.md>), [memory](<https://devfeed.tech/tags/memory.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisories](<https://devfeed.tech/tags/security-advisories.md>), [socket](<https://devfeed.tech/tags/socket.md>), [ssrf](<https://devfeed.tech/tags/ssrf.md>), [update](<https://devfeed.tech/tags/update.md>), [url](<https://devfeed.tech/tags/url.md>), [validation](<https://devfeed.tech/tags/validation.md>), [webhook](<https://devfeed.tech/tags/webhook.md>)

### AI overview

Two vulnerabilities affect Ruby's bundled `resolv` gem: CVE-2026-80212 can cause unbounded memory growth from attacker-controlled DNS responses, and CVE-2026-80213 can bypass hostname checks when an overlong hostname is resolved. The bypass does not affect validation that rejects names over 255 octets or labels over 63 octets. Exposure requires name resolution through `resolv`; ordinary socket connections using the OS resolver are not affected, and Net::HTTP loading the gem alone does not indicate exposure. Check application code and dependencies for `Resolv` use or `resolv-replace`. Upgrade to `resolv` 0.7.2, or 0.3.2 for Ruby 3.3. Ruby 3.2's bundled 0.2.x line has no planned release; install 0.7.2 instead.

### Source excerpt

Two vulnerabilities have been discovered in the resolv gem bundled with Ruby. They have been assigned the CVE identifiers CVE-2026-80212 and CVE-2026-80213. We recommend upgrading the resolv gem. CVE-2026-80212: Memory exhaustion through malicious DNS responses An application that resolves a hostname an attacker can influence, such as a webhook target or a user-supplied URL, can be made to consume memory without bound. The attacker points a domain at a name server they control and returns responses that the library retains permanently. Repeated lookups grow the process until it runs out of memory and the service stops. CVE-2026-80213: Hostname validation bypass An application that checks a hostname against an allow list or an SSRF filter and then resolves it can be made to look up a domain other than the one it checked. The string that passes validation and the name that reaches the network are not the same, so the connection can end up at a host the application never approved. This requires a hostname that exceeds the DNS length limits, so validation that rejects names longer than 255 octets, or labels longer than 63 octets, is not affected. Affected versions resolv gem 0.4.0 through 0.7.1 resolv gem 0.3.1 and earlier The version bundled with Ruby differs per series: Ruby 4.0 ships resolv 0.7.0, Ruby 3.4 ships 0.7.1, and Ruby 3.3 ships 0.3.1. What to check Only code that resolves names through this gem is affected. Ordinary socket connections, including Net::HTTP and anything built on TCPSocket, use the operating system resolver and are not. Net::HTTP does load the gem, but only for its IP address regular expressions, so a loaded gem is not by itself a sign of exposure. An application reaches the affected code by calling Resolv itself, by loading resolv-replace, which routes all socket name resolution through the gem, or through a dependency that resolves names this way. Check your dependencies as well as your own code. Recommended action Update the resolv gem to 0

## From YAGNI to YDNIY

DevFeed: [From YAGNI to YDNIY](<https://devfeed.tech/articles/from-yagni-to-ydniy-20994.md>)

Original publisher: [Read original article](<https://codewithoutrules.com/2020/09/18/ydniy/>)

Author: Itamar Turner-Trauring

Published: 2020-09-18T00:00:00Z

Content type: article

Language: en

Sources: [Itamar Turner-Trauring](<https://devfeed.tech/sources/itamar-turner-trauring.md>)

Topics: [Deployment-Driven Development](<https://devfeed.tech/topics/deployment-driven-development.md>), [Software](<https://devfeed.tech/topics/software.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [2020](<https://devfeed.tech/tags/2020.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [conda](<https://devfeed.tech/tags/conda.md>), [data-scientists](<https://devfeed.tech/tags/data-scientists.md>), [jupyter](<https://devfeed.tech/tags/jupyter.md>), [jupyter-notebooks](<https://devfeed.tech/tags/jupyter-notebooks.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [memory](<https://devfeed.tech/tags/memory.md>), [native](<https://devfeed.tech/tags/native.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [packaging](<https://devfeed.tech/tags/packaging.md>), [program](<https://devfeed.tech/tags/program.md>), [python](<https://devfeed.tech/tags/python.md>), [real-world](<https://devfeed.tech/tags/real-world.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>)

### AI overview

YDNIY ("You Don't Need It Yet") means delaying features that are clearly useful but aren't required to release a product that already helps some users. The author illustrates this with Fil, a Python memory profiler first released with Linux-only support for complete program runs and the most popular allocation APIs. Later releases added macOS, more allocation APIs, out-of-memory support, faster performance, Jupyter support, and Conda installation. Shipping earlier let people use Fil while development continued, and each release expanded its usefulness. The excerpt says YAGNI can justify dropping features that are not clearly necessary; YDNIY instead postpones features when the product remains useful without them. The source excerpt ends before the full decision flowchart and comparison with Minimum Viable Product.

### Source excerpt

How do you ship a product on schedule? One useful approach is applying the You Ain't Gonna Need It principle, or YAGNI for short: leave out all the things that seem nice-to-have, but you have no proof you actually need. But beyond the things you don't need, there are still plenty of features you pretty clearly do need... but are not blockers on releasing your product. So beyond YAGNI, there's also YDNIY: You Don't Need It Yet. Let's see an example of this principle in practice, visualize the principle as a flowchart, and then compare it to another popular acronymed concept, the Minimum Viable Product. A real world example: shipping a new memory profiler In March 2020 I shipped the initial release of a new memory profiler for Python, Fil. Here's how it changed over time in terms of features, from May to August 2020: 0.3.0, initial release: Installable via pip packaging tool, runs only on Linux, only profiles complete program runs. 0.3.3: Support for an additional memory allocation API. 0.4.0: Support for out-of-memory situations. 0.5.0: macOS support. 0.6.0: Support for mmap() allocation API. 0.7.0: Support for C++ memory allocation API. 0.9.0: Much faster and lower overhead in some use cases, added support for yet another memory allocation API. 0.10.0: Support for running inside Jupyter notebooks, and native support for installing via the Conda packaging tool. All of the features I added in later releases were clearly necessary from the start; YAGNI did not apply. Lots of people use macOS, the target audience of data scientists and scientists often use Conda and Jupyter, all those memory allocation APIs are used in the real world, and so on. But even a tool that only runs complete programs on Linux, and only tracks the most popular memory allocation APIs, is still useful to some people. If I had waited until all those features were implemented to ship an initial release, all the people who used the profiler during the first four months of its existence would have had

## Services. The life with/without. And WorkManager.

DevFeed: [Services. The life with/without. And WorkManager.](<https://devfeed.tech/articles/services-the-life-with-without-and-workmanager-26129.md>)

Original publisher: [Read original article](<https://medium.com/google-developer-experts/services-the-life-with-without-and-worker-6933111d62a6?source=rss-8735065c2497------2>)

Author: Yonatan (Yoni) Levin

Published: 2018-05-10T17:53:59Z

Content type: article

Language: en

Sources: [Yonatan V. Levin](<https://devfeed.tech/sources/stories-by-yonatan-v-levin-on-medium.md>)

Topics: [Process](<https://devfeed.tech/topics/process.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [background](<https://devfeed.tech/tags/background.md>), [google](<https://devfeed.tech/tags/google.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [oom](<https://devfeed.tech/tags/oom.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [pages](<https://devfeed.tech/tags/pages.md>), [processes](<https://devfeed.tech/tags/processes.md>), [processing](<https://devfeed.tech/tags/processing.md>), [ram](<https://devfeed.tech/tags/ram.md>), [releases](<https://devfeed.tech/tags/releases.md>), [star-wars](<https://devfeed.tech/tags/star-wars.md>), [state](<https://devfeed.tech/tags/state.md>), [system](<https://devfeed.tech/tags/system.md>), [workmanager](<https://devfeed.tech/tags/workmanager.md>)

### AI overview

The excerpt explains that Android has no swap space and uses the OOM Killer to free memory when resources run low. Activity Manager assigns processes scores based on application state; higher scores make a process more likely to be killed, subject to configurable free-memory thresholds. The article frames this memory-management background as context for comparing existing background-work solutions and WorkManager, but the supplied text ends before those sections provide details.

### Source excerpt

With recent Android releases dealing with background, it has become more complicated than ever. Much like the Star Wars plot, it has become more and more intertwined And so, Google has released WorkManager as part of JetPack -- to help us to deal with such a background. Before learning what WorkManager is -- it's essential to understand why we need it and what was a reasons behind building it. The developers who knows what happens under the hood of the components/libraries and understand why they use it -- is by far a better developers. Better developer It's going to be a long article, so prepare a good cup of coffee & a couple of cookies. It build in 3 parts: Part #1 -- Memory Basics Part #2 -- Existing Background Solutions Part #3 -- WorkManager Firstly, before starting with all background-ish things -- we need to understand some of the basics of Android processing memory management. And this is will be our first part: Part 1: Android Memory 101 A long, long time ago, in a galaxy far far away -- Android kernel was first developed it and it was based on Linux-Kernel. The main difference between Android and all other Linux-Kernel based systems is that Android does not have a thing called "Swap space." Swap space in Linux is used when the amount of physical memory (RAM) is full. If the system needs more memory resources and the RAM is full, inactive pages in memory are moved to the swap space. While swap space can help machines with a small amount of RAM, it should not be considered a replacement for more RAM. Swap space is located on hard drives, which have a slower access time than physical memory In Android, there is no such a thing as a "Swap space." When the system is running out of memory, it's using OOM Killer to save a galaxy. Out Of Memory Killer The guy's goal is to free up memory by killing the processes based on their "visibility state" and amount of memory consumed. Every process gave its oom_adj score by Activity Manager. It's a combination of application state