# A dependency finding is settled by the resolved version, the packaging and a call site, each checked with a command

Guide, 19 Nov 2026, read 19 Nov 2026

**The short answer.** Ask the build tool for the resolved version, compare it with the advisory's affected and not-affected rows, inspect how the artifact is packaged, then search for a call site fed by untrusted data. For fastjson CVE-2026-16723, the string 1.2.83 gave not affected as a noneautotype build and affected as a plain pin; 1.2.84 is the fix.

## The resolved version comes from the build tool, not the manifest

Maven's documentation defines the term: "Maven avoids the need to discover and specify the libraries that your own dependencies require by including transitive dependencies automatically." A manifest states what the team asked for. The build tool states what shipped, and a transitive copy only shows up there. In Maven, mvn dependency:tree -Dincludes=com.alibaba prints just the matching branches. In npm, npm ls followed by the package name does the same. For a library bundled inside a runtime, such as Brotli in Node.js, the check is node --version on each image.

The service team runs the command in CI or on the built artifact. The record is the command, its output and the date, pasted into the ticket. The step fails when someone reads the manifest instead, or runs the command on one module of a multi-module build and misses a copy that arrives through another.

## Worked pass one: fastjson CVE-2026-16723 in a Spring Boot service

The fastjson advisory, dated 21 Jul 2026 and updated 29 Jul 2026, lists 1.2.68 to 1.2.83 as affected and 1.2.84 as the fix. The trigger needs AutoType off, SafeMode off and a Spring Boot executable fat-jar. CVE-2026-16723 is not in the CISA KEV feed dated 18 Nov 2026, so the urgency comes from the [CVSS](/methods/severity-score/) 3.1 base score of 9.0 and the reachability answer, not from known exploitation; its [EPSS](/methods/exploit-prediction/) of 0.0066 is low.

To get real tool output we built a Spring Boot 3.3.5 service on 19 Nov 2026 whose only fastjson arrives through com.alibaba.csp:sentinel-transport-common 1.8.6, then ran mvn dependency:tree -Dincludes=com.alibaba. It printed:

[INFO] demo:orders-api:jar:1.0.0
[INFO] \- com.alibaba.csp:sentinel-transport-common:jar:1.8.6:compile
[INFO]    \- com.alibaba:fastjson:jar:1.2.83_noneautotype:compile

The version reads 1.2.83, inside the affected range. The artifact is the noneautotype build, and the advisory's not-affected table has a row for it: "noneautotype builds", reason "Vulnerable code removed at compile time". A scanner that trims the suffix would flag this service. The tree output settles it, and the ticket records the artifact name.

Then we pinned com.alibaba:fastjson to 1.2.83 in dependencyManagement and ran the same command: the tree showed com.alibaba:fastjson:jar:1.2.83:compile. Pinning to 1.2.84 showed 1.2.84. The three outcomes:

| Resolved artifact | What the advisory says | Outcome | Action and owner |
| --- | --- | --- | --- |
| fastjson 1.2.83_noneautotype, through sentinel-transport-common 1.8.6 | noneautotype builds: vulnerable code removed at compile time | Not affected by CVE-2026-16723 | Service team records the tree output and the advisory row, then closes |
| fastjson 1.2.83, pinned in dependencyManagement | 1.2.68 to 1.2.83 affected when the app is a fat-jar with AutoType and SafeMode off | Affected if a call site parses untrusted JSON | Service team upgrades to 1.2.84, or sets -Dfastjson.parser.safeMode=true until the release ships |
| fastjson 1.2.84 | Fixed: type names with URL-special characters are rejected | Not affected | Close with the tree output |

## The packaging check decides whether the trigger can happen at all

The advisory names a deployment form, so read it from the built artifact. On the test service with fastjson pinned to 1.2.83, unzip -p target/orders-api-1.0.0.jar META-INF/MANIFEST.MF printed Main-Class: org.springframework.boot.loader.launch.JarLauncher, and unzip -l showed BOOT-INF/lib/fastjson-1.2.83.jar nested inside. That is the executable fat-jar shape. The advisory's not-affected table lists "plain java -jar, uber-jar, Tomcat/Jetty WAR" as not meeting the trigger condition, so the same code built as a WAR for Tomcat falls in that row.

The platform team usually knows the packaging from the pipeline. Record the manifest line, because packaging changes when someone switches build plugins. The step fails when the check is run on the source tree or a local build instead of the artifact that is deployed.

## A call site that parses untrusted JSON makes the finding real

Search the service source with grep -rnE "JSON\.(parse|parseObject)\(" src/main and classify each hit by where the string comes from. Request bodies, queue messages and upstream responses count. A parse of a file bundled in the jar does not. The advisory warns that "Specifying a target class (e.g., JSON.parseObject(body, SomeDto.class) ) is not a mitigation", so a typed call still counts when the class has Object or Map fields.

The code owner writes the list of file and line with a conclusion for each. A static reachability tool can build the same list across many services where it supports the language, and reflection can hide calls from it, so a clean result is evidence, not proof. The step fails in both directions: reflection hides a real call, and a hit on a test class or a bundled file raises a finding that cannot be triggered. The four-question tool on the home page records this search as its first question, is the code called. When that is the only open answer and the service is reached with no control in front, the tool names static reachability, or runtime reachability on a running workload.

## Worked pass two: Brotli CVE-2026-111497 in a Node.js service

The Node.js security release of 21 Oct 2026 covers lines 26.x, 24.x and 22.x and says an attacker who can supply Brotli data that an application decompresses with node:zlib can corrupt process memory. Fixed releases are v22.23.4, v24.22.1 and v26.12.1. CISA added the CVE to KEV on 27 Oct 2026, six days after the release, so this one is a known-exploited finding.

On a v22.23.5 runtime, node --version printed v22.23.5, later than the fixed v22.23.4. Compare the Node.js release number with the advisory's list and record that. The embedded string node -p "process.versions.brotli" is not a test: ELLIO reports it shows 1.2.0 on patched and vulnerable Node.js builds alike, because the fix was cherry-picked without changing the version string.

For a runtime below the fixed release, the next question is the call path. We installed got 11.8.6 and ran npm ls decompress-response, which printed got@11.8.6 and decompress-response@6.0.0. In the installed source, got sets accept-encoding to gzip, deflate, br when process.versions.brotli is a string, and decompress-response calls zlib.createBrotliDecompress() when the reply says content-encoding br. Any service that uses got to call an upstream therefore decompresses Brotli from that upstream, and the attacker condition becomes whether someone can control or alter that upstream reply.

The decision follows from that. If the runtime is below the fixed release and a Brotli path exists, the ticket names the fixed release for the line as the target and cites the KEV date. Until the upgrade ships, the vendor mitigation is to avoid negotiating or decompressing br from untrusted peers. If no path exists, record the grep and the npm ls output, and still schedule the upgrade, since the vulnerable decoder remains in the runtime.

## Four cases where the version string gives the wrong answer

Two are above: the fastjson artifact suffix and the Node.js Brotli string. A third is that an older release can be unaffected: the fastjson advisory says versions up to 1.2.60 lack the vulnerable code path. A fourth is that a short affected list can still apply to you. The Apache Tomcat security pages list CVE-2026-34486 as affecting only 11.0.20, 10.1.53 and 9.0.116, the three releases that carried a flawed fix for CVE-2026-29146, and it matters only when a cluster uses EncryptInterceptor. Apache fixed it in 11.0.21, 10.1.54 and 9.0.117. The checks are catalina.sh version and grep -n EncryptInterceptor conf/server.xml on each node. CISA listed the CVE on 4 Aug 2026.

A package unused in one service is still resolved by the others, so run the commands per service.

## The ticket carries the evidence, the decision and the owner

Fields to fill: the resolved version and the command that showed it; the packaging line from the manifest; the call sites with a conclusion each; the decision (upgrade, interim control, or not affected with the advisory row cited); the target version; the owner and the date. A reader who gets that ticket six months later can see which fact decided the outcome. The step fails when the ticket says "not affected" without the advisory row or the command output behind it.

## Related pages

- [Triaging an internet-facing appliance finding](/guides/triaging-an-internet-facing-appliance-finding/)
- [Reading a vendor advisory's preconditions](/guides/reading-a-vendor-advisory/)
- [How agent investigation records its evidence](/guides/how-agent-investigation-records-its-evidence/)

## Sources

- fastjson security advisory for CVE-2026-16723: https://github.com/alibaba/fastjson2/wiki/Security-Advisory:-Remote-Code-Execution-in-fastjson-1.2.68%E2%80%931.2.83 (read 19 Nov 2026)
- NVD record for CVE-2026-16723: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-16723 (read 19 Nov 2026)
- Maven Central listing for com.alibaba:fastjson: https://repo1.maven.org/maven2/com/alibaba/fastjson/ (read 19 Nov 2026)
- Node.js October 2026 security releases: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (read 19 Nov 2026)
- NVD record for CVE-2026-111497: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-111497 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-111497: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-111497 (read 19 Nov 2026)
- npm registry entry for got: https://registry.npmjs.org/got (read 19 Nov 2026)
- NVD record for CVE-2026-34486 (Apache Tomcat): https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-34486 (read 19 Nov 2026)
- CISA KEV feed, dated 18 Nov 2026: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- Apache Maven: Introduction to the dependency mechanism: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html (read 19 Nov 2026)
- ELLIO on CVE-2026-111497 (process.versions.brotli and patched builds): https://ellio.tech/en/blog/node2shell-cve-2026-111497-rce-on-stock-nodejs-builds/ (read 19 Nov 2026)
- Apache Tomcat 11 security page (CVE-2026-34486, fixed in 11.0.21; the 10 and 9 pages give 10.1.54 and 9.0.117): https://tomcat.apache.org/security-11.html (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/guides/triaging-a-dependency-finding/
