newarray accepted any element-type byte and multianewarray accepted zero dimensions, both of which the JVM refuses. The decoder now stops at a newarray whose type isn't one of the eight primitive array types or a multianewarray with zero dimensions, as for other invalid instructions.
Any object that was the string "$null" was read as the archive's nil marker, so a real string with that text disappeared. Only the archive's first object, where the marker lives, is now read as nil; a "$null" string anywhere else stays a string.
DNS labels showed dots, backslashes and unprintable bytes as they came, so different wire names could look the same; they're now escaped (\. \\ \DDD). HTTP is reported only for a complete start line: a request with a known method, a target without control characters and an HTTP/1.x version, or a response with an HTTP/1.x version, a three-digit status and an optional reason phrase. The packet tools' warning about unreadable parts now says what may be missing.
In a ZIP64 archive with data in front of it, the locator's stored offset can miss the end record, and the classic fallback then counted the ZIP64 record and locator as prefix bytes and lost the central directory. Before falling back, the reader now looks for the record within 64 KiB before the locator, and takes it only when it is single-volume, agrees with the classic record and has a central directory right before it; a warning says it was recovered.
Small ext4 inline files had their contents read as block addresses, so they failed to recover or came out as zeros, and a filesystem with only the inline-data feature was labelled ext2. Regular inline files of up to 60 bytes are now read from the inode, within the usual byte budget; longer inline files and inline directories are still reported as not recovered.
After a bad extent header or an unreadable child block, the extent walker returned a partly filled map, and recovery showed the missing ranges as zeros. Extent nodes now have to be complete and consistent (magic, entry counts, child depths, non-empty extents), within a shared work budget, or the file is left unrecovered with a warning.
LZ4 SquashFS images were refused although the project has a bounded raw LZ4 decoder. SquashFS metadata, data blocks and tail fragments now decode with it, treating the size as an upper limit, while Unity bundles keep requiring the exact decoded size.
Data blocks were concatenated whatever their length and the result trimmed at the end, so a short or corrupt first block could shift the bytes after it while the file looked complete. Each raw or decoded block, sparse blocks and the last partial block included, must now cover exactly its part of the file, or the file is left unrecovered with a warning.
The application graph is built from the assembly's inventory, members and native boundaries but only passed on the members' warnings, so a warning only the inventory or the native mappings raised (such as trailing bytes in an attribute's signature) disappeared from it. The graph now combines all three, keeps each view's first warning in view, and removes repeats before its 20-warning limit.
Directory and file pointers in a version-two cramfs image could reach bytes appended after the filesystem, so unrelated trailing data could fill in recovered contents. The size recorded in a version-two header now bounds every read, in either byte order; an image shorter than that size is read as far as it goes and marked incomplete, and version-one images are read as before.
Any ext inode that wasn't a directory or symlink was read as a regular file, so device, socket and FIFO fields could be taken as block pointers. The inode's mode now decides its kind: special and unknown inodes are listed as other entries without reading their fields as data, and a directory entry's type hint can't override the inode.
The certificate reader took any [0] field inside SignedData, kept non-X.509 certificate choices, and applied the certificate limit per field. It now reads the certificates field only in its declared place after the version, digest algorithms and content, returns only X.509 (SEQUENCE) choices, and applies the limit once.
#1644 sent an earlier run's waiting notes as the new run's message and deleted their files, so a run that stopped during setup lost them, and a note file that couldn't be read was dropped silently. Such notes now become the new run's own waiting notes, kept on disk until the builder takes them or handed to the next run like any note; a notes folder that can't be read is moved aside instead of deleted.
The ZIP64 end record's declared size wasn't checked. A record smaller than its fixed fields, an extent that overflows, or fixed fields that run into the locator now make the archive corrupt; a declared extent that doesn't end at the locator, or a locator that doesn't point to a record (as in archives with a stub in front), keeps reading the directory with a warning, as before.
The XML plist reader already decodes UTF-16 after either byte-order mark, but the check that decides a file is a plist only looked for ASCII <plist, so UTF-16 NIB archives were turned away first. The check now also finds the UTF-16LE and UTF-16BE marker after its byte-order mark, on code-unit boundaries, within the same 1 KiB probe.
A type chunk whose entry data started inside its offset table or past the chunk was still read, and a bag entry with a short header, or more values than fit in the chunk, read past its data. The type is now skipped with a warning in the first case; in the second the entry is kept without its parent and values, the table is marked truncated, and a warning says why. A bag with more values than the reader keeps is marked truncated too.
Binary plist dates and keyed-archive NSDate values were shown floored to whole seconds, so events within one second looked the same. They now keep their fraction, rounded to microseconds (finer would only show the float's noise for present-day dates), with a rounded-up second carried into the date; whole seconds still show without a fraction.
A data node that failed to inflate, used an unsupported compression or decoded to a length other than its declared size was skipped, leaving zeros or older bytes in the file while it looked recovered, and an overlong raw node could overwrite the next extent. Such nodes now mark their extent damaged; a newer valid node can still replace it, and a file is left unrecovered only if a damaged extent survives into its final contents.
The DER reader accepted redundant length encodings (a long form under 128, or a leading zero length byte) without saying so. Each element now records whether its length is minimal; certificate, CMS, Authenticode and certificate-chain views keep everything they read and add one note that an element is not strict DER, and signatures over those bytes are checked as before.
Lossy decoding turned different malformed name values into the same replacement characters, and UniversalString values weren't decoded. Name values are now decoded by their string type (UTF-8; Printable, IA5, Visible and Numeric as ASCII; T61 as Latin-1; BMP and UniversalString as UTF-16 and UTF-32), and a value that is malformed or of another type is shown as its hex DER encoding.
Signature readers returned the decoded signature and silently accepted bytes after it. Complete method, field, local, TypeSpec and instantiation signatures now note when their blob carries extra bytes: the decoded types are kept, as the runtime uses them, and the inventory, member and native-boundary views say once that some signatures have trailing data that wasn't interpreted.
Godot reads --path as UTF-8, and the path was passed through a lossy conversion, so a project folder whose name isn't valid UTF-8 could open a different project with a similar name. Such a project now isn't launched instead.
Resource configurations that differed only in grammatical gender, round screens, wide colour gamut, HDR, or keyboard and navigation visibility got the same qualifier string, and MNC 00 was shown as 65535. Those qualifiers are now named as Android names them.
The contract dispatcher patterns accepted instructions a few positions apart, so unrelated code could be read as selector extraction, a Vyper selector comparison or a short-calldata check. Each pattern now needs its exact instruction sequence and operands, and a dispatch to something that isn't a JUMPDEST reports its mutability as unknown.
ZIP entries made on macOS (host 19) now keep their Unix mode, so their directories and symlinks are recognised, and VFAT entries (host 14) are recognised as directories by their DOS attribute, as MS-DOS and NTFS entries already were.
Searches for where a class is used missed lambdas, method handles, method types, class literals and dynamic constants. ldc and invokedynamic now link through the class's BootstrapMethods table to the method handle and static arguments they use, reported at the instruction that loads or calls them, within a shared work limit.
SVCB and HTTPS answers (priority, target, ALPN, port and address hints; unknown keys kept as hex), NAPTR, DNAME, SSHFP, TLSA and URI records now show their values instead of a byte count. A record that doesn't decode marks its message incomplete, keeping the answers before it, as other records do.
A bound import's module or forwarder name was read up to 256 bytes from its offset, even past the end of the directory. A name now has to end inside the directory, or it's reported as outside it, as the other bound-import checks are.
A note sent during a build waits in the inbox for the builder's next step; if the app closed before the builder took it, the next run deleted it as it started (#1620). The note's file now also keeps the person's own words, how the feed shows them and the pictures, and a run started without a message sends what an earlier run left waiting, oldest first, before the folder is cleared, as the app already does with notes a finished run didn't get to.
The XZ decoder expected the file to end right after one stream's footer, so valid .xz files with several streams or the standard four-byte padding were refused. It now finds each stream's bounds from the end, through its checksummed footer and index, and decodes them in order under one output budget; index integers, declared sizes and padding alignment are checked, and every read of the input is bounds-checked. SquashFS blocks keep the single-stream decoder, as before.
PF_A2B10G10R10 and PF_FloatR11G11B10 textures couldn't be exported. The shared pixel decoder now reads both: 10-bit red, green and blue with two-bit alpha, and unsigned 11/11/10-bit floats shown as sRGB like the other float formats.
Unity's EAC_R, EAC_R_SIGNED, EAC_RG and EAC_RG_SIGNED textures were recognised but couldn't be exported. The shared pixel decoder now reads EAC's 11-bit channel blocks (modifier tables, column-major selectors and the zero-multiplier rule), showing one channel as grey and two as red and green, with signed values mapped so zero is mid-grey.
A rank-one general ARRAY signature was shown like a vector (int[]), and declared sizes and signed lower bounds were dropped, so different managed types looked the same. Type names now keep the general-array form (int[*] at rank one), each dimension, and explicit bounds (int[0...2], int[-1...]), in method, field, local, generic and nested-array names.
A repeated metadata key could overwrite the reported model identity, and a repeated tensor name could inflate the parameter total; display truncation and retention caps could hide the repeat. The reader now tracks complete keys and tensor names and reports a file that repeats one as malformed, as the format's own loader does.
The cramfs reader gave up on any file with a direct block pointer. It now follows them: the shifted start address, uncompressed blocks of the expected size, and compressed blocks prefixed by their two-byte length, in both byte orders, with ordinary blocks after a direct one starting where it ended. Bounds and output limits are as before.
The ext reader took every symlink shorter than 60 bytes as stored inline, so a short target kept in a data block was read from the block-pointer bytes and came out wrong. It now tells inline targets from block-backed ones by the inode's allocated blocks, allowing for extended attributes, ext4 allocation units and large block counts; inline-data symlinks are reported as not read, and a target whose data can't be read stays unknown, with its declared length kept.
Signed branch and switch displacements were cast back to unsigned offsets even when the destination lay before the method or past its last byte, so invalid targets reached control-flow analysis. Short branches, long branches and every switch destination are now checked against the body; an invalid one stops decoding before that instruction with a reported issue, keeping the instructions decoded before it.
Normal, delay-load and bound import readers now stop at the end of the file bytes their directory maps to, require complete descriptor and forwarder records, and mark the table truncated with a warning when they don't get them. A normal import table that runs past its declared Size, or has Size 0, is still read to its terminator, as Windows does, with a warning. Names and forwarders outside the bound import directory are reported instead of read from beyond it. The resource reader shares the same mapping-length helper, unchanged.
`core_evidence_exports_compare` indexes each operation/subject by a single record. Normal exports can contain several observations of that subject, including different text pages or successive versions of the same address annotation. Later index insertions silently overwrite earlier observations, so additions and removals disappear, changing record order changes the comparison, and one intact page can hide a tampered page from the changed count.
The AArch64 address tracker kept an old value after an addition with an unknown register, read unknown memory indices as zero, could keep a stale base after a load with writeback or a stale link register after a call, and did W-register additions in 64 bits, so stale values could name a later indirect call as an import its instructions didn't establish. Address facts are now kept only when the operands prove them: unknown addends and indices clear the result, W additions wrap at 32 bits, every register an instruction writes is forgotten before new facts are recorded, and calls clear the link register too.
The application graph recognizes a worker entry point but then follows its spawn edge while assigning the parent's role. Worker modules, their ordinary dependencies and their endpoint evidence consequently appear as `main`, `page` or `package`. The later worker-role pass cannot correct a role that was already assigned. Use the existing worker/service-worker/utility-process edge classification to stop parent-role traversal at execution-context boundaries. Worker roots still receive their own role and propagate it through ordinary imports. Spawn edges remain in the graph, and a module also directly imported by the parent retains the existing role precedence.
A package with 52 reachable modules loses the final module's role when each hop repeats the same `require()` 2,000 times. The graph resolves those imports, but role propagation charges its 100,000-step limit for duplicate queue entries, eventually leaving reachable modules as `unknown`. Mark modules in the existing role map before enqueueing them. Repeated imports, cycles and shared dependencies then use one queue entry per newly discovered module. The limit remains 100,000 newly discovered modules per assignment, and the existing main/preload/renderer/page/worker precedence stays intact. Inline scripts continue to inherit their page's role.
The token scanner ended `//` comments only at LF. A bare CR, U+2028 or U+2029 therefore hid following executable code inside the comment. That dropped imports, IPC and fetch facts in lexer fallback and prevented the parser admission check from seeing excessive nesting after the comment. Recognize every JavaScript line terminator when scanning line comments, skip Unicode terminators before charging the token budget, and stop identifiers at those boundaries. Strings, templates and block comments keep their existing handling.
A module keyed by `0x10` and a loader call written as `16` produced different identities. Numeric separators and exponent notation caused the same problem, including dangling `requires` targets in the application graph. Different spellings of one numeric dependency could also occupy separate list entries. Use the existing syntax library's JavaScript number conversion for numeric module keys, loader arguments, browserify mappings and chunk IDs. Explicitly enable its already-present `to_js_string` feature. String identifiers retain their literal spelling, including strings such as `"0x10"` that identify a different property from numeric `0x10`.
A text-read page that reached the last line of a file but cut a line at the 256 KiB limit reported cut_lines correctly, yet its coverage said complete because it was worked out from the line count alone. Coverage is now partial whenever a line on the page was cut.
Function studies identify their source bytes, but `app_call_path_find` currently joins their addresses without checking that source identity. Two different binaries can therefore contribute different edges at the same addresses and produce a call path that exists in neither binary. The regression uses two real ELF targets: one has main → helper, the other has helper → dispatch, and neither contains the complete main → dispatch path. Both inline records and saved evidence references reproduce the false path.
With FEAT_PAuth_LR and PSTATE.PACM set, RETAA and RETAB use x16 as an extra modifier. The decoder knows neither the CPU's features nor PSTATE, so authenticated returns now also record a possible read of x16, beside their link register and stack pointer, and value flow keeps that input.
The input loaders trust an earlier file-size report before reading to EOF. A regular virtual file can report zero bytes and still return data beyond the configured limit, and files can grow between the size check and read. Some loaders accept devices or pipes, allowing a text or evidence-bundle request to wait indefinitely for a writer. Prefix reads also use metadata size to decide whether to assign a whole-file hash, so a truncated prefix of a zero-size-reporting file is misidentified as the whole input.
A native function can branch to a body block placed before its entry address. The control-flow graph already included that block, but reference and string scans only looked from the entry onward, and parameter inference took the lowest-address block as the entry, so a register set by the real entry could become a false parameter while the real input disappeared. Reference scans now cover the address range of all of the function's body blocks, and parameters are read from the block at the function's actual entry.