dbcve.org
M9l65a FirmwareOperating system · Hp

CVE-2026-1997

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 001.2602a / 001.2602b or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain HP OfficeJet Pro printers may expose information if Cross‑Origin Resource Sharing (CORS) is misconfigured, potentially allowing unauthorized web origins to access device resource. CORS is disabled by default on Pro‑class devices and can only be enabled by an administrator through the Embedded Web Server (EWS). Keeping CORS disabled unless explicitly required helps ensure that only trusted solutions can interact with the device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HP OfficeJet Pro printers with CORS enabled through the Embedded Web Server (EWS) may improperly allow cross-origin requests from untrusted web origins, potentially exposing sensitive device information to unauthorized parties. The vulnerability exists when administrators enable CORS without proper origin restrictions.

MitigationVerify CORS is disabled in the EWS; if enabled for legitimate purposes, restrict allowed origins to only trusted domains and disable when no longer needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
M9l65a FirmwareOperating system
Affected:< 001.2602a
D9l20a FirmwareOperating system
Affected:< 001.2602b
K7s32a FirmwareOperating system
Affected:< 001.2602b
D9l21a FirmwareOperating system
Affected:< 001.2602b
K7s42a FirmwareOperating system
Affected:< 001.2602b
T0g65a FirmwareOperating system
Affected:< 001.2602b
K7s39a FirmwareOperating system
Affected:< 001.2602b
J6x83a FirmwareOperating system
Affected:< 001.2602b

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the printer model
    Access the printer's Embedded Web Server (EWS) by entering the printer's IP address in a web browser. Locate the model number, typically found on the main page or under the 'General' or 'Information' section.
    Affected if The printer model is one of: M9l65a, D9l20a, K7s32a, D9l21a, K7s42a, T0g65a, K7s39a, or J6x83a.
  2. Check the installed firmware version
    In the EWS, navigate to the 'General' or 'Firmware Information' page to view the current firmware version. Alternatively, print a configuration or status page from the printer control panel.
    Affected if The firmware version is below 001.2602a for M9l65a, or below 001.2602b for all other affected models.
  3. Verify if CORS is enabled in the EWS
    Log into the EWS as an administrator. Navigate to the 'Settings', 'Security', or 'Network' sections. Look for a CORS (Cross-Origin Resource Sharing) setting or configuration option.
    Affected if CORS is enabled on the printer.
  4. Inspect CORS origin restrictions
    In the same EWS section where CORS is configured, examine the allowed origins list. Determine whether any origins are permitted or if the configuration allows requests from any origin.
    Affected if CORS is enabled and either no origin restrictions are defined or origins from untrusted or arbitrary web domains are permitted.

If the printer model matches an affected product, the firmware version is below the specified threshold, and CORS is enabled with no or weak origin restrictions, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 001.2602a / 001.2602b or later
Fixed in 001.2602a001.2602b
Interim mitigation

Verify CORS is disabled in the EWS; if enabled for legitimate purposes, restrict allowed origins to only trusted domains and disable when no longer needed.

Recommended fix High confidence

Firmware version 001.2602a or later for M9l65a; Firmware version 001.2602b or later for D9l20a, K7s32a, D9l21a, K7s42a, T0g65a, K7s39a, J6x83a

  1. 1. Identify the exact printer model from the affected list (M9l65a, D9l20a, K7s32a, D9l21a, K7s42a, T0g65a, K7s39a, or J6x83a)
  2. 2. Access the printer's Embedded Web Server (EWS) by entering the printer's IP address in a web browser
  3. 3. Navigate to the Settings or General section to check the current firmware version
  4. 4. Download the latest firmware update from HP Support (support.hp.com) for your specific printer model
  5. 5. In the EWS, locate the Firmware Update section and upload/install the new firmware (version 001.2602a or later for M9l65a; version 001.2602b or later for all other affected models)
  6. 6. After firmware update completes, access EWS again and verify CORS configuration under Security or Network settings
  7. 7. Confirm CORS is disabled (recommended) or properly configured to allow only trusted origins if business requirements demand it
Caveat Firmware updates on HP printers typically retain settings, but verify critical configurations (network settings, admin credentials) after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in M9l65a Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1997 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data