{"id":"CVE-2026-104872","aliases":["CLSA-2026-1794411722","CLSA-2026-1794423718","CLSA-2026-1794423755","CLSA-2026-1794424748","CLSA-2026-1794425732","CLSA-2026-1794426507","CLSA-2026-1794427289","CLSA-2026-1794438580","CLSA-2026-1794439548","CLSA-2026-1794439665","CLSA-2026-1794439793","CLSA-2026-1794439943","EUVD-2026-91788","GHSA-qqmp-wf37-98f9"],"status":"published","title":"Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute","description":"OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages.","severity":{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00244,"percentile":0.15797,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-532"],"published":"2026-10-02T19:50:24Z","modified":"2026-11-12T01:15:02Z","fixes":[{"ecosystem":"npm","package":"@opentelemetry/instrumentation-cassandra-driver","fixed_in":["0.66.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-tedious","fixed_in":["0.40.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-oracledb","fixed_in":["0.46.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-mongoose","fixed_in":["0.67.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql","fixed_in":["0.67.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-knex","fixed_in":["0.65.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql2","fixed_in":["0.67.0"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@opentelemetry/instrumentation-pg","fixed_in":["0.73.0"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-pg","fixed_in":["0.36.2-tuxcare.1","0.43.0-tuxcare.1"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-tedious","fixed_in":["0.27.0-tuxcare.1"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-cassandra-driver","fixed_in":["0.44.0-tuxcare.1","0.40.0-tuxcare.4"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql2","fixed_in":["0.34.5-tuxcare.1","0.40.0-tuxcare.1","0.44.0-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql","fixed_in":["0.34.5-tuxcare.2","0.40.0-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mongoose","fixed_in":["0.33.4-tuxcare.1","0.40.0-tuxcare.3"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-cassandra-driver","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.66.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-tedious","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.40.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-oracledb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.46.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-mongoose","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-knex","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.65.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@opentelemetry/instrumentation-pg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.73.0"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-pg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.36.2-tuxcare.0"},{"fixed":"0.36.2-tuxcare.1"}]}],"versions":["0.36.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-tedious","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.27.0-tuxcare.0"},{"fixed":"0.27.0-tuxcare.1"}]}],"versions":["0.27.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-cassandra-driver","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.44.0-tuxcare.0"},{"fixed":"0.44.0-tuxcare.1"}]}],"versions":["0.44.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-pg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.43.0-tuxcare.0"},{"fixed":"0.43.0-tuxcare.1"}]}],"versions":["0.43.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.34.5-tuxcare.0"},{"fixed":"0.34.5-tuxcare.1"}]}],"versions":["0.34.5"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.40.0-tuxcare.0"},{"fixed":"0.40.0-tuxcare.1"}]}],"versions":["0.40.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.44.0-tuxcare.0"},{"fixed":"0.44.0-tuxcare.2"}]}],"versions":["0.44.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.34.5-tuxcare.0"},{"fixed":"0.34.5-tuxcare.2"}]}],"versions":["0.34.5"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.40.0-tuxcare.0"},{"fixed":"0.40.0-tuxcare.2"}]}],"versions":["0.40.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mongoose","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.33.4-tuxcare.0"},{"fixed":"0.33.4-tuxcare.1"}]}],"versions":["0.33.4"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-mongoose","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.40.0-tuxcare.0"},{"fixed":"0.40.0-tuxcare.3"}]}],"versions":["0.40.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@opentelemetry/instrumentation-cassandra-driver","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.40.0-tuxcare.0"},{"fixed":"0.40.0-tuxcare.4"}]}],"versions":["0.40.0"]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-cassandra-driver","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.66.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-tedious","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.40.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-oracledb","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.46.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-mongoose","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-knex","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.65.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-mysql2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.67.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@opentelemetry/instrumentation-pg","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.73.0"}]}]}],"products":[{"vendor":"@opentelemetry","product":"instrumentation-cassandra-driver"},{"vendor":"@opentelemetry","product":"instrumentation-knex"},{"vendor":"@opentelemetry","product":"instrumentation-mongoose"},{"vendor":"@opentelemetry","product":"instrumentation-mysql"},{"vendor":"@opentelemetry","product":"instrumentation-mysql2"},{"vendor":"@opentelemetry","product":"instrumentation-oracledb"},{"vendor":"@opentelemetry","product":"instrumentation-pg"},{"vendor":"@opentelemetry","product":"instrumentation-tedious"},{"vendor":"open-telemetry","product":"opentelemetry-js-contrib"}],"references":[{"url":"https://github.com/open-telemetry/opentelemetry-js-contrib/security/advisories/GHSA-qqmp-wf37-98f9","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3585","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/open-telemetry/opentelemetry-js-contrib/commit/27e172a9e0d549559056ccd58f27d13467454156","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/open-telemetry/opentelemetry-js-contrib/commit/5b7dd0e102e940d653e04b08b5a1b721a8271037","tags":["x_refsource_MISC","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104872","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-qqmp-wf37-98f9"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104872.json","tags":["advisory"]},{"url":"https://github.com/open-telemetry/opentelemetry-js-contrib","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-104872","title":"Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute","description":"OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages.","status":"published","published":"2026-10-02T19:50:24.868Z","modified":"2026-10-06T16:40:55.44Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T14:20:09.448255Z"}],"euvd":[{"id":"EUVD-2026-91788","description":"OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages.","status":"published","published":"2026-10-02T19:50:24Z","modified":"2026-10-06T16:40:55Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T17:27:37.140631Z"}],"ghsa":[{"id":"GHSA-qqmp-wf37-98f9","title":"Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute","description":"### Impact\n\nMultiple `@opentelemetry/instrumentation-*` packages recorded the database connection username as the `db.user`\nspan attribute on every instrumented database operation. This attribute was emitted unconditionally — it was\nnot gated by `enhancedDatabaseReporting` or any other opt-in flag, and it was the **default** behaviour for\nall users of the affected packages until the patched releases shipped on 2026-07-23.\n\nThe attribute is forwarded to every configured observability backend (Jaeger, Zipkin, Datadog, OTLP\ncollectors, etc.).  Depending on the database account naming convention in use, the exported value may\nreveal:\n\n- Internal service account names that disclose architecture topology.\n- Role-encoded usernames (e.g. `admin_readwrite`, `app_readonly_prod`) useful for privilege inference.\n- Database account naming patterns useful for credential enumeration.\n\nAffected packages (all are vulnerable from the first published version through the version listed below):\n\n| Package | Vulnerable range | Patched version |\n|---------|-----------------|-----------------|\n| `@opentelemetry/instrumentation-cassandra-driver` | `\u003c 0.66.0` | `0.66.0` |\n| `@opentelemetry/instrumentation-knex`             | `\u003c 0.65.0` | `0.65.0` |\n| `@opentelemetry/instrumentation-mongoose`         | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-mysql`            | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-mysql2`           | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-oracledb`         | `\u003c 0.46.0` | `0.46.0` |\n| `@opentelemetry/instrumentation-pg`               | `\u003c 0.73.0` | `0.73.0` |\n| `@opentelemetry/instrumentation-tedious`          | `\u003c 0.40.0` | `0.40.0` |\n\n### Patches\n\nFixed in the coordinated release on 2026-07-23 via\n[feat!: only emit stable http, network and database attributes (#3585)](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3585).\n\nUpgrade to the patched version listed in the table above for each instrumentation package in use.\n\n### Workarounds\n\nNo configuration-level workaround exists in the affected versions: the `db.user` attribute cannot be\nsuppressed without patching. As a partial mitigation, a custom `SpanProcessor` can be used to strip `db.user` from spans before they leave the process:\n\n```ts\n// Example: drop db.user in a custom SpanProcessor\nclass StripDbUserProcessor implements SpanProcessor {\n  onStart(span: Span) {\n    span.setAttribute('db.user', null);\n  }\n  onEnd() {}\n  shutdown() { return Promise.resolve(); }\n  forceFlush() { return Promise.resolve(); }\n}\n```\n\nUsers who control the downstream collector can also filter the attribute at the collector pipeline level.","status":"published","published":"2026-10-05T22:52:44Z","modified":"2026-10-05T22:52:47Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T14:41:25.889593Z"}],"nvd":[{"id":"CVE-2026-104872","description":"OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages.","status":"published","published":"2026-10-02T20:17:01.067Z","modified":"2026-10-06T17:17:16.147Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T14:12:53.75133Z"}],"osv":[{"id":"CVE-2026-104872","title":"Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute","description":"OpenTelemetry JavaScript Contrib provides instrumentation libraries for collecting telemetry from JavaScript applications. Prior to versions 0.66.0 of @opentelemetry/instrumentation-cassandra-driver, 0.65.0 of @opentelemetry/instrumentation-knex, 0.67.0 of @opentelemetry/instrumentation-mongoose, @opentelemetry/instrumentation-mysql, and @opentelemetry/instrumentation-mysql2, 0.46.0 of @opentelemetry/instrumentation-oracledb, 0.73.0 of @opentelemetry/instrumentation-pg, and 0.40.0 of @opentelemetry/instrumentation-tedious, the packages add the database connection username to every instrumented database operation as the db.user span attribute. The attribute is emitted by default and is not controlled by enhancedDatabaseReporting or another opt-in setting. Configured observability backends therefore receive database account names that may expose service topology, role or environment information, and account naming patterns. This issue is fixed in versions 0.66.0, 0.65.0, 0.67.0, 0.46.0, 0.73.0, and 0.40.0 of the respective packages.","status":"published","published":"2026-10-02T19:50:24.868Z","modified":"2026-11-09T02:46:57.848471286Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-532"],"updated_at":"2026-11-09T03:16:24.800471Z"},{"id":"GHSA-qqmp-wf37-98f9","title":"Multiple @opentelemetry/instrumentation-* packages expose database username via unconditional db.user span attribute","description":"### Impact\n\nMultiple `@opentelemetry/instrumentation-*` packages recorded the database connection username as the `db.user`\nspan attribute on every instrumented database operation. This attribute was emitted unconditionally — it was\nnot gated by `enhancedDatabaseReporting` or any other opt-in flag, and it was the **default** behaviour for\nall users of the affected packages until the patched releases shipped on 2026-07-23.\n\nThe attribute is forwarded to every configured observability backend (Jaeger, Zipkin, Datadog, OTLP\ncollectors, etc.).  Depending on the database account naming convention in use, the exported value may\nreveal:\n\n- Internal service account names that disclose architecture topology.\n- Role-encoded usernames (e.g. `admin_readwrite`, `app_readonly_prod`) useful for privilege inference.\n- Database account naming patterns useful for credential enumeration.\n\nAffected packages (all are vulnerable from the first published version through the version listed below):\n\n| Package | Vulnerable range | Patched version |\n|---------|-----------------|-----------------|\n| `@opentelemetry/instrumentation-cassandra-driver` | `\u003c 0.66.0` | `0.66.0` |\n| `@opentelemetry/instrumentation-knex`             | `\u003c 0.65.0` | `0.65.0` |\n| `@opentelemetry/instrumentation-mongoose`         | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-mysql`            | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-mysql2`           | `\u003c 0.67.0` | `0.67.0` |\n| `@opentelemetry/instrumentation-oracledb`         | `\u003c 0.46.0` | `0.46.0` |\n| `@opentelemetry/instrumentation-pg`               | `\u003c 0.73.0` | `0.73.0` |\n| `@opentelemetry/instrumentation-tedious`          | `\u003c 0.40.0` | `0.40.0` |\n\n### Patches\n\nFixed in the coordinated release on 2026-07-23 via\n[feat!: only emit stable http, network and database attributes (#3585)](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3585).\n\nUpgrade to the patched version listed in the table above for each instrumentation package in use.\n\n### Workarounds\n\nNo configuration-level workaround exists in the affected versions: the `db.user` attribute cannot be\nsuppressed without patching. As a partial mitigation, a custom `SpanProcessor` can be used to strip `db.user` from spans before they leave the process:\n\n```ts\n// Example: drop db.user in a custom SpanProcessor\nclass StripDbUserProcessor implements SpanProcessor {\n  onStart(span: Span) {\n    span.setAttribute('db.user', null);\n  }\n  onEnd() {}\n  shutdown() { return Promise.resolve(); }\n  forceFlush() { return Promise.resolve(); }\n}\n```\n\nUsers who control the downstream collector can also filter the attribute at the collector pipeline level.","status":"published","published":"2026-10-05T22:52:44Z","modified":"2026-10-05T23:00:05.311085601Z","cvss":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-532"],"updated_at":"2026-11-02T15:46:54.760124Z"},{"id":"CLSA-2026-1794411722","title":"TuxCare security update for @opentelemetry/instrumentation-pg (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-pg to address 1 CVE. Fixed in 0.36.2-tuxcare.1.","status":"published","published":"2026-11-11T16:42:03Z","modified":"2026-11-11T19:30:05.294401472Z","updated_at":"2026-11-11T19:50:24.684142Z"},{"id":"CLSA-2026-1794423718","title":"TuxCare security update for @opentelemetry/instrumentation-tedious (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-tedious to address 1 CVE. Fixed in 0.27.0-tuxcare.1.","status":"published","published":"2026-11-11T20:01:59Z","modified":"2026-11-12T01:15:02.178786356Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794423755","title":"TuxCare security update for @opentelemetry/instrumentation-cassandra-driver (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-cassandra-driver to address 1 CVE. Fixed in 0.44.0-tuxcare.1.","status":"published","published":"2026-11-11T20:02:36Z","modified":"2026-11-12T01:15:02.186524016Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794424748","title":"TuxCare security update for @opentelemetry/instrumentation-pg (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-pg to address 1 CVE. Fixed in 0.43.0-tuxcare.1.","status":"published","published":"2026-11-11T20:19:09Z","modified":"2026-11-12T01:15:02.825693608Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794425732","title":"TuxCare security update for @opentelemetry/instrumentation-mysql2 (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mysql2 to address 1 CVE. Fixed in 0.34.5-tuxcare.1.","status":"published","published":"2026-11-11T20:35:33Z","modified":"2026-11-12T01:15:02.191905164Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794426507","title":"TuxCare security update for @opentelemetry/instrumentation-mysql2 (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mysql2 to address 1 CVE. Fixed in 0.40.0-tuxcare.1.","status":"published","published":"2026-11-11T20:48:27Z","modified":"2026-11-12T01:15:02.182122384Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794427289","title":"TuxCare security update for @opentelemetry/instrumentation-mysql2 (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mysql2 to address 1 CVE. Fixed in 0.44.0-tuxcare.2.","status":"published","published":"2026-11-11T21:01:28Z","modified":"2026-11-12T01:15:02.188300529Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794438580","title":"TuxCare security update for @opentelemetry/instrumentation-mysql (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mysql to address 1 CVE. Fixed in 0.34.5-tuxcare.2.","status":"published","published":"2026-11-12T00:09:41Z","modified":"2026-11-12T01:15:02.172760205Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794439548","title":"TuxCare security update for @opentelemetry/instrumentation-mysql (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mysql to address 1 CVE. Fixed in 0.40.0-tuxcare.2.","status":"published","published":"2026-11-12T00:25:49Z","modified":"2026-11-12T01:15:02.178331832Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794439665","title":"TuxCare security update for @opentelemetry/instrumentation-mongoose (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mongoose to address 1 CVE. Fixed in 0.33.4-tuxcare.1.","status":"published","published":"2026-11-12T00:27:46Z","modified":"2026-11-12T01:15:02.837967949Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794439793","title":"TuxCare security update for @opentelemetry/instrumentation-mongoose (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-mongoose to address 1 CVE. Fixed in 0.40.0-tuxcare.3.","status":"published","published":"2026-11-12T00:29:54Z","modified":"2026-11-12T01:15:02.82735314Z","updated_at":"2026-11-12T01:25:17.040581Z"},{"id":"CLSA-2026-1794439943","title":"TuxCare security update for @opentelemetry/instrumentation-cassandra-driver (1 CVE)","description":"TuxCare rebuilt @opentelemetry/instrumentation-cassandra-driver to address 1 CVE. Fixed in 0.40.0-tuxcare.4.","status":"published","published":"2026-11-12T00:32:24Z","modified":"2026-11-12T01:15:02.196278073Z","updated_at":"2026-11-12T01:25:17.040581Z"}]}}