Skip to main content
Participant
Oct 30, 2026 4:44 AM UTC
Answered

Node.js vulnerability scan

Hi all,

We're currently investigating a vulnerability finding relating to Node.js 22.22.2 in relation to CVE-2026-111497, which appears to be bundled with Adobe Creative Cloud.

Has anyone else encountered this finding, or does anyone know whether the bundled version is actually exposed to this vulnerability based on how Adobe uses Node.js?

It would also be helpful to know whether Adobe plans to update the bundled Node.js version in an upcoming Creative Cloud update, and whether there is any official guidance regarding the risk or impact of CVE-2026-111497 in this particular implementation.

If any Adobe representatives are active here, an official clarification would be greatly appreciated.

Thanks!

    Tariq Ahmad DarCorrect answer
    Community Manager
    Nov 20, 2026 11:32 AM UTC

    Hi all,

     

    Thank you for your patience and for the detail you have shared. We understand how frustrating it is to deal with a scan finding that stays open, especially when you have already spent time on it.

    We checked with the internal team about CVE-2026-111497. The response received is that Adobe proactively notifies customers of industry wide or third party vulnerabilities if its investigations determine a notifiable impact to Adobe’s systems or customer data. Adobe does not respond to inquiries concerning such vulnerabilities if its investigations determine that there is no impact to Adobe’s systems or customer data.

    For that reason, we are not able to share a release timeline or investigation details in this thread. What you can do:

    Please let us know if you have any other questions, and we will be happy to assist further.


    Thanks,
    Tariq Ahmad

    11 replies

    Tariq Ahmad DarCommunity ManagerCorrect answer
    Community Manager
    Nov 20, 2026 11:32 AM UTC

    Hi all,

     

    Thank you for your patience and for the detail you have shared. We understand how frustrating it is to deal with a scan finding that stays open, especially when you have already spent time on it.

    We checked with the internal team about CVE-2026-111497. The response received is that Adobe proactively notifies customers of industry wide or third party vulnerabilities if its investigations determine a notifiable impact to Adobe’s systems or customer data. Adobe does not respond to inquiries concerning such vulnerabilities if its investigations determine that there is no impact to Adobe’s systems or customer data.

    For that reason, we are not able to share a release timeline or investigation details in this thread. What you can do:

    Please let us know if you have any other questions, and we will be happy to assist further.


    Thanks,
    Tariq Ahmad

    Translate
    Participant
    Nov 5, 2026 2:05 PM UTC

    Adobe Supports response…

    “ As checked with the team, Creative Cloud desktop apps are native C++ desktop applications rather than public Node.js HTTP servers, meaning the bundled Node.js component is generally not exposed to untrusted network-controlled Brotli streams. We advise users not to manually replace bundled binaries inside installation directories, as it is unsupported and can break application stability.
     
    Adobe Experience Manager and Edge Delivery Services do not use Node.js in their public-facing request-handling runtimes; Node.js is restricted to internal build pipelines (such as compiling front-end assets) which are not exposed to the internet or arbitrary Brotli-encoded requests.
     
    Mitigation & Recommendations
     
    ·         Do not manually swap binaries: Replacing files inside Adobe's installation folders manually can lead to corruption or app failure.
    Check official updates: Monitor official security bulletins via the Adobe Security Bulletins & Advisories Page or report specific path findings directly to Adobe PSIRT (psirt@adobe.com).
    Adobe Trust Center: Security bulletins and advisories
    Official Node.js Patch Target: If managing standalone Node.js environments rather than bundled vendor apps, upgrade Node.js 22.x line to 22.23.4 or later.”

    Not great.

    Translate
    Participant
    Nov 3, 2026 6:10 PM UTC

    Hi team, Could you please let us know the expected release date for the patched version of Adobe that addresses this security vulnerability (CVE)?

    We would prefer to apply the official Adobe patch rather than spend additional time on R&D to modify the Node.js binaries within Adobe’s bundled directories.

    Please share the anticipated timeline for the fix so that we can plan accordingly.

     

    Translate
    Community Manager
    Oct 30, 2026 1:00 PM UTC

    Hi ​@angular_Flair2fa1, 

    Thanks for the detailed report. We’ll forward this internally to the appropriate team for review.

    In the meantime, you can also report this directly to Adobe’s Product Security Incident Response Team at psirt@adobe.com, including the Node.js version, the exact file/component path you identified, and your scan details. You can also check Adobe’s official Security Bulletins & Advisories page for any bulletin once published: https://adobe.ly/4yMMXpb

    We’ll make sure this is tracked through the appropriate channel.

     

    ​@kglad, just to clarify, this specific CVE was only made public in October 2026, so it’s a new report, not something that’s been sitting unaddressed for over a year. Replacing the bundled Node.js file yourself isn’t something we can confirm is safe or recommend, even if it hasn’t caused visible problems for some users.


    Thanks,
    Tariq

    Translate
    Participant
    Nov 3, 2026 6:11 PM UTC

    Hi ​@Tariq Ahmad Dar  Could you please let us know the expected release date for the patched version of Adobe that addresses this security vulnerability (CVE)?

    We would prefer to apply the official Adobe patch rather than spend additional time on R&D to modify the Node.js binaries within Adobe’s bundled directories.

    Please share the anticipated timeline for the fix so that we can plan accordingly.

    Translate
    Community Manager
    Nov 3, 2026 7:15 PM UTC

    Hi ​@stylish_vibrancybe25,

    Thank you for following up, and we understand how important it is to have a clear timeline so your team can plan the remediation.

    As ​@Tariq Ahmad Dar mentioned earlier, your report has been forwarded internally to the appropriate team for review. We’re not able to share an expected release date in this thread, but the channels below will help you get an official update:

    1. Report it to PSIRT: Since this finding came from your own scan, please forward the complete report to Adobe’s Product Security Incident Response Team, using the contact Tariq shared earlier in this thread. Please include the Node.js version, the exact file path your scan flagged, and your scan details. How to report a security issue is covered on the Adobe Trust Center: https://adobe.ly/4zq2bBr

    2. Watch for security bulletins: Adobe security bulletins from October 2026 onward are published on that same Trust Center page. If a bulletin is released that applies to this finding, it will be listed there with the corrective actions to take. You can also subscribe on that page to be notified of new bulletins.

    We’d also ask that you do not modify the bundled Node.js files yourselves. We can’t confirm that replacing them is safe, and we don’t recommend it.

    Please let us know if you have any other questions, we’re happy to help.

    Thanks,
    ^AV

    Translate
    kglad
    Community Expert
    Community Expert
    Oct 30, 2026 12:11 PM UTC

    yes, it’s been noted for over 1 year.  users have found that then can replace their older node.js with the latest version and cause no adobe issues.  why adobe hasn’t done this, i do not know.

    Translate
    notta
    Participant
    Nov 4, 2026 6:21 PM UTC

    I’ve done this twice now and the vulnerable version is put back within a day. This is happening without running updates. This is unbelievable as it’s the product that puts the file on the system to begin with. They patch the application but won’t update node.exe. Well then it’s up to us to fix it. We fix it twice but it keeps putting the vulnerable node.exe back.

    Translate