Volatility 3
Source availableActive
Volatility 3 is a Python framework for extracting digital artefacts from volatile memory (RAM) samples, independent of the system under investigation. Its published symbol-table packs cover Windows, Mac and Linux only. Neither the README nor the symbol-table documentation mentions Android. The documentation says Linux and Mac images need a symbol table whose banner matches the image exactly, and a 2026 DFRWS EU paper describes generating Volatility 3 profiles for modern Android phones from BTF debug information.
Facts
| Website | github.com |
|---|---|
| Vendor | Volatility Foundation |
| Licence | Source available (Volatility Software License (VSL) v1.0, a custom licence with source-publication obligations for changes and additions (GitHub reports 'Other'); the Volatility Software License 1.0 is not on the OSI list of approved licences (https://opensource.org/licenses; the list's 'Vovida Software License v. 1.0', SPDX VSL-1.0, is a different licence)) |
| Category | Analysis |
| Functions | Analysis, Parsing |
| Targets | Android, Linux, Windows, macOS |
| Runs on | Windows, macOS, Linux |
| Pricing | Free |
| Users | Research, Law enforcement, Open-source DFIR community, Corporate |
| Last activity | 2026-09 · v2.28.2 release (2026-09-17); commits continue to 2026-10-12 [github.com] |
| GitHub activity | volatilityfoundation/volatility3 · 4,585 stars · last push 2026-10-12 · latest release v2.28.2 (2026-09-17) · checked 2026-11-10 |
Capabilities
- Framework for extracting digital artefacts from volatile memory samples; the extraction techniques run independently of the system being investigated. [github.com]
- Symbol table packs are published for Windows, Mac and Linux. [github.com]
- Linux and Mac symbol tables can be generated from a DWARF file using dwarf2json. [volatility3.readthedocs.io]
- A 2026 DFRWS EU paper (Oliveri et al.) reports adapting a method for generating Volatility 3 profiles from BTF debug information emitted by the kernel at runtime, and in a simulated scenario on a real GKI Android phone recovering contact details from the memory of a terminated password manager. [eurecom.edu]
Limitations
- For Linux/Mac images Volatility 3 requires the banner in the symbol-table JSON to match the banner in the image exactly, including compilation time and gcc version; a kernel with debugging symbols is the only suitable means of recovering the information most plugins need, and the documentation says a generic table is not guaranteed to produce accurate results. [volatility3.readthedocs.io]
- The same paper states that on hardened Linux and modern GKI Android systems (Secure Boot, kernel lockdown, module signing policies) traditional open-source acquisition tools such as LiME and AVML are no longer viable, so obtaining a physical memory dump is a separate problem from analysing it. [eurecom.edu]
- The README's quick start and symbol-pack list name Windows, Mac and Linux; it gives no Android or iOS support statement. [github.com]
Links
Related tools
- Ghidra · App analysis
- Plaso (log2timeline) · Analysis
Sources
- Volatility 3 README (github.com)
- Volatility 3 documentation: symbol tables (volatility3.readthedocs.io)
- Volatility Software License v1.0 (volatilityfoundation.org)
- LEMON: eBPF-based memory acquisition for modern Android (Oliveri et al., DFRWS EU 2026) (eurecom.edu)
- Volatility 3 v2.28.2 release (github.com)
- GitHub: volatilityfoundation/volatility3 commits (github.com)
- Open Source Initiative: licenses (approved licence list) (opensource.org)
Reviewed . Spotted an error? See the corrections policy.