vuln-osv update 2026-11-13T00:44:09Z
This commit is contained in:
Vulnerability Bot committed
1 parent
8a2c5b2e77
commit
ccfb9c50cb
167 files changed
+200
-83
No files matched your search
@@ -1 +1 @@
|
||||
{"schema_version":"1.9.0","id":"GHSA-22fx-6r9m-r8h9","published":"2023-05-05T18:30:17Z","modified":"2025-01-29T22:00:08Z","aliases":["CVE-2023-29659"],"summary":"libheif vulnerable to segmentation fault via floating point exception","details":"A Segmentation fault caused by a floating point exception exists in libheif 1.15.1 using crafted heif images via the heif::Fraction::round() function in box.cc, which causes a denial of service.","affected":[{"package":{"name":"github.com/strukturag/libheif","ecosystem":"Go","purl":"pkg:golang/github.com/strukturag/libheif"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.15.2"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/05/GHSA-22fx-6r9m-r8h9/GHSA-22fx-6r9m-r8h9.json"}}],"references":[{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-29659"},{"type":"WEB","url":"https://github.com/strukturag/libheif/issues/794"},{"type":"WEB","url":"https://github.com/strukturag/libheif/commit/e05e15b57a38ec411cb9acb38512a1c36ff62991"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L"},{"type":"PACKAGE","url":"github.com/strukturag/libheif"}],"database_specific":{"cwe_ids":["CWE-369"],"github_reviewed":true,"github_reviewed_at":"2023-06-02T21:18:04Z","nvd_published_at":"2023-05-05T16:15:09Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H"}]}
|
||||
{"schema_version":"1.9.2","id":"GHSA-22fx-6r9m-r8h9","published":"2023-05-05T18:30:17Z","modified":"2026-11-12T22:45:03.578496051Z","aliases":["CVE-2023-29659"],"summary":"libheif vulnerable to segmentation fault via floating point exception","details":"A Segmentation fault caused by a floating point exception exists in libheif 1.15.1 using crafted heif images via the heif::Fraction::round() function in box.cc, which causes a denial of service.","affected":[{"package":{"name":"github.com/strukturag/libheif","ecosystem":"Go","purl":"pkg:golang/github.com/strukturag/libheif"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.15.2"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/05/GHSA-22fx-6r9m-r8h9/GHSA-22fx-6r9m-r8h9.json"}}],"references":[{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-29659"},{"type":"WEB","url":"https://github.com/strukturag/libheif/issues/794"},{"type":"WEB","url":"https://github.com/strukturag/libheif/commit/e05e15b57a38ec411cb9acb38512a1c36ff62991"},{"type":"PACKAGE","url":"https://github.com/strukturag/libheif"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CKAE6NQBA3Q7GS6VTNDZRZZZVPPEFUEZ"},{"type":"WEB","url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LGKHDCS4HRZE3UGXYYDYPTIPNIBRLQ5L"}],"database_specific":{"cwe_ids":["CWE-369"],"github_reviewed":true,"github_reviewed_at":"2023-06-02T21:18:04Z","nvd_published_at":"2023-05-05T16:15:09Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H"}]}
|
||||
@@ -0,0 +1 @@
|
||||
{"schema_version":"1.9.2","id":"GHSA-5qg5-rgp6-j5m5","published":"2026-11-12T20:37:38Z","modified":"2026-11-12T20:45:03.505205185Z","aliases":["CVE-2026-125327"],"summary":"pgEdge RAG Server unbounded corpus read allows resource exhaustion from unauthenticated requests","details":"### Impact\n\nAn unauthenticated caller able to reach the query endpoint could exhaust database and server resources with ordinary, inexpensive requests.\n\nThe keyword-search arm read the entire corpus on every request and rebuilt an in-memory BM25 index from it, so the cost of serving a query scaled with the size of the source table rather than with the size of the result set. Each request cost the server and the tenant's database far more than it cost the caller to make, which makes this a materially more effective denial-of-service lever than flooding the endpoint with ordinary requests. The amplification factor grows with corpus size, so the largest deployments are the most exposed.\n\nHybrid search was enabled by default and configured per pipeline rather than per request, so a caller could not opt out of the keyword arm and an operator could not leave it available to some requests but not others.\n\n**Who is affected:** any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, whose query endpoint is reachable by an untrusted party. The endpoint required no authentication and applied no rate limiting.\n\nIn `1.0.0`, `internal/database/search.go:130` built the corpus query with no `LIMIT`:\n\n```go\nquery = fmt.Sprintf(`\n SELECT ...\n FROM %s%s`,\n tableIdent,\n filterClause)\n```\n\n`FetchDocuments` accepted no limit parameter at all, so neither a caller nor the orchestrator had any way to bound the read.\n`internal/config/loader.go:197` defaulted `HybridEnabled` to true, and `internal/server/middleware.go:37` applied only logging, panic recovery and optional CORS.\n\n### Patches\n\n**Fixed in `2.0.0`. Upgrade to `2.0.0` or later.**\n\nReads are capped by a new per-pipeline `search.bm25_max_documents`, defaulting to 10000, plumbed through `SearchBackend.FetchDocuments` and applied as a parameterised `LIMIT`. There is deliberately no unlimited value: a non-positive setting is rejected at configuration load time rather than silently treated as unbounded.\n\nRequests that reach the cap are logged, because keyword recall is partial at that point and an operator should not have to infer it. A new `disable_hybrid` request field lets a caller skip the expensive arm per query, and can only ever turn it off.\n\n**After upgrading, review the default `search.bm25_max_documents` value of 10000 against the size of your corpus.** A cap far below corpus size silently reduces keyword recall.\n\n### Workarounds\n\nPlace the server behind an authenticating, rate-limiting reverse proxy.\n\nSetting `hybrid_enabled: false` on each pipeline removes the keyword arm and with it the unbounded read, at the cost of keyword recall. This is the only mitigation available without a proxy.\n\nNeither is a substitute for upgrading.","affected":[{"package":{"name":"github.com/pgEdge/pgedge-rag-server","ecosystem":"Go","purl":"pkg:golang/github.com/pgEdge/pgedge-rag-server"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260729020411-a09d4872356b"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-5qg5-rgp6-j5m5/GHSA-5qg5-rgp6-j5m5.json"}}],"references":[{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/security/advisories/GHSA-5qg5-rgp6-j5m5"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-125327"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/pull/44"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/commit/a09d4872356b510c81f11591845445c33ff45a84"},{"type":"PACKAGE","url":"https://github.com/pgEdge/pgedge-rag-server"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/releases/tag/v2.0.0"}],"database_specific":{"cwe_ids":["CWE-405","CWE-770"],"github_reviewed":true,"github_reviewed_at":"2026-11-12T20:37:38Z","nvd_published_at":"2026-11-10T19:21:09Z","severity":"HIGH"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"}]}
|
||||
@@ -0,0 +1 @@
|
||||
{"schema_version":"1.9.2","id":"GHSA-68g8-gh8f-7rhg","published":"2026-11-12T20:29:32Z","modified":"2026-11-12T20:45:03.499008369Z","aliases":["CVE-2026-125326"],"summary":"pgEdge RAG Server discloses part of the configured provider credential through API error messages","details":"### Impact\n\nAn unauthenticated remote caller could read part of the operator's configured LLM provider API key.\n\nThe query API relayed the text of a provider error straight to the caller. That text carried the upstream provider's own message, and providers characteristically quote a partially masked form of the credential they rejected when authentication fails — so a failing provider call published a fragment of the operator's key. A caller who can reach the endpoint can cause such a failure and read the result.\n\n**Who is affected:** any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, whose query endpoint was reachable by an untrusted party. The endpoint carries no authentication in the affected versions.\n\nThe disclosed material authenticates to a **third-party provider account** rather than to pgEdge software, which is why the severity carries Scope: Changed.\n\n`v1.0.0:internal/server/handlers.go:121` relayed `err.Error()` to the client when pipeline execution failed. `parseError` in\n`v1.0.0:internal/llm/openai/client.go` produced that error by two routes, and both disclose:\n\n```go\nvar errResp ErrorResponse\nif err := json.Unmarshal(body, &errResp); err != nil {\n return fmt.Errorf(\"API error (status %d): %s\", resp.StatusCode, string(body))\n}\nreturn fmt.Errorf(\"API error (status %d): %s\", resp.StatusCode, errResp.Error.Message)\n```\n\nThe first branch interpolates the entire unparsed response body. The second returns the provider's own message, which for OpenAI quotes the `sk-proj-` prefix and the final four characters of the submitted key.\n\n### Patches\n\n**Fixed in `2.0.0`. Upgrade to `2.0.0` or later.**\n\nThe fix adds `internal/safeerr` and stops provider error text reaching API clients.\n\n**Upgrading does not undo the disclosure, and this needs action beyond upgrading. Rotate any LLM provider credential that was configured on an affected version while the endpoint was reachable by an untrusted caller**, particularly if that provider was rejecting the key at the time. A fragment already disclosed stays disclosed.\n\n### Workarounds\n\nPlace the server behind a proxy that rewrites 5xx response bodies, or terminate provider errors before they reach the API surface. Keeping provider credentials valid, so that no authentication failure is produced, also avoids the disclosure in practice.\n\nNone of these removes the underlying defect, and none is a substitute for upgrading.","affected":[{"package":{"name":"github.com/pgEdge/pgedge-rag-server","ecosystem":"Go","purl":"pkg:golang/github.com/pgEdge/pgedge-rag-server"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260729022402-72e0785a6d7c"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-68g8-gh8f-7rhg/GHSA-68g8-gh8f-7rhg.json"}}],"references":[{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/security/advisories/GHSA-68g8-gh8f-7rhg"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-125326"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/pull/45"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/commit/72e0785a6d7cc9e35ad67d570bc9fddeaa4b2f61"},{"type":"PACKAGE","url":"https://github.com/pgEdge/pgedge-rag-server"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/releases/tag/v2.0.0"}],"database_specific":{"cwe_ids":["CWE-209","CWE-522"],"github_reviewed":true,"github_reviewed_at":"2026-11-12T20:29:32Z","nvd_published_at":"2026-11-10T18:17:34Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"}]}
|
||||
@@ -0,0 +1 @@
|
||||
{"schema_version":"1.9.2","id":"GHSA-8835-xmqj-354h","published":"2026-11-12T19:32:36Z","modified":"2026-11-12T19:45:03.182304314Z","aliases":["CVE-2026-125328"],"summary":"pgEdge Go LLM Library discloses provider API key fragments in error messages","details":"### Impact\n\nAn unauthenticated caller could read part of the operator's configured LLM provider API key.\n\nThe library's own health handler pings every configured provider using the operator's real credential and returns the resulting error text verbatim. Providers characteristically quote a partially masked form of the credential they rejected, so a failing ping published a fragment of\nthe key.\n\n**The endpoint is unauthenticated by default.** `authorize()` returns\ntrue immediately when the consuming application sets no `Authorize` hook,\nso `GET /v1/health` is reachable by anyone who can reach the listening\nport unless the consumer opted in to authentication.\n\n**Who is affected:** any application embedding pgedge-go-llm-lib at\n`0.1.0` or `0.1.1` that exposes the bundled HTTP proxy without setting an\n`Authorize` hook. Both affected versions are released tags and resolve\nthrough the public Go module proxy.\n\nThe disclosed material authenticates to a **third-party provider\naccount** rather than to pgEdge software, which is why the severity\ncarries Scope: Changed.\n\nEvidence at `v0.1.1`: `llm/proxy/handlers.go:296` (`handleHealth`\nreturning `err.Error()` in `ProviderHealth.Error`), `llm/proxy/proxy.go:247`\n(`authorize()` defaulting to permit), and `llm/proxy/proxy.go:350`\n(`writeError` writing the error with no redaction).\n\n### Patches\n\n**Fixed in `0.2.0`. Upgrade to `0.2.0` or later**, which redacts\ncredentials from provider error messages unconditionally. The fix adds\n`llm/internal/redact`, with a follow-up anchoring word boundaries, and is\npinned by tests in that package.\n\n**Note the version.** There is no `0.1.2` — it was never cut, and some\nearlier material named it in error. `0.2.0` is the first fixed release.\n\n**Upgrading does not undo a disclosure that already happened. Rotate any\nLLM provider credential configured on an affected version** where the\nproxy was reachable without an `Authorize` hook, particularly if a\nprovider was rejecting that key at the time.\n\n### Workarounds\n\nSet an `Authorize` hook on the proxy, which closes the unauthenticated\nroute to the health endpoint. Restricting network access to the listening\nport limits who can reach it. Neither removes the underlying disclosure\nfor a caller who does reach the endpoint.","affected":[{"package":{"name":"github.com/pgEdge/pgedge-go-llm-lib","ecosystem":"Go","purl":"pkg:golang/github.com/pgEdge/pgedge-go-llm-lib"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.1.2-0.20260729024727-7531a55d368b"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-8835-xmqj-354h/GHSA-8835-xmqj-354h.json"}}],"references":[{"type":"WEB","url":"https://github.com/pgEdge/pgedge-go-llm-lib/security/advisories/GHSA-8835-xmqj-354h"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-125328"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-go-llm-lib/pull/26"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-go-llm-lib/commit/7531a55d368b3a29cd173c792cc4609c4134b076"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-go-llm-lib/commit/8bb9a6380d5f8db0124b51605759897034ad4da1"},{"type":"PACKAGE","url":"https://github.com/pgEdge/pgedge-go-llm-lib"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-go-llm-lib/releases/tag/v0.2.0"}],"database_specific":{"cwe_ids":["CWE-209","CWE-522"],"github_reviewed":true,"github_reviewed_at":"2026-11-12T19:32:36Z","nvd_published_at":"2026-11-10T19:21:10Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"}]}
|
||||
@@ -0,0 +1 @@
|
||||
{"schema_version":"1.9.2","id":"GHSA-vq9p-w6wv-cr25","published":"2026-11-12T20:46:03Z","modified":"2026-11-12T21:00:03.623455832Z","aliases":["CVE-2026-125323"],"summary":"pgEdge Control Plane generates pg_hba.conf with trust authentication for local and loopback connections","details":"### Summary\n\nEvery `pg_hba.conf` generated by the pgEdge Control Plane begins with a hard-coded block of `trust` entries covering Unix-socket and loopback connections. Any operating-system account that can reach the Postgres socket or the loopback interface on a database host can authenticate as any Postgres role, including the superuser, without presenting a credential.\n\n### Details\n\nThe generated file opens with the following six entries:\n\n```\nlocal all all trust\nhost all all 127.0.0.1/32 trust\nhost all all ::1/128 trust\nlocal replication all trust\nhost replication all 127.0.0.1/32 trust\nhost replication all ::1/128 trust\n```\n\nPostgres evaluates `pg_hba.conf` top-down and stops at the first matching rule. Because these entries are emitted at the top of the file, they also pre-empt every rule below them — including entries supplied by an operator through the `pg_hba_conf` field of a database node specification, which are appended lower in the file and are therefore never reached for local or loopback connections.\n\nBoth supported orchestrators emit these entries, but exposure differs by deployment model:\n\n* **systemd** — the database runs on a shared multi-user host. Any local account\n on that host can connect as the Postgres superuser. This is the\n higher-severity case and the one the CVSS score below reflects.\n* **Docker Swarm** — the Unix socket and the loopback interface belong to the\n Postgres container, so reaching these entries requires code execution inside\n that container. Publishing the Postgres port to the host does not change this:\n such connections are not seen by Postgres as originating from `127.0.0.1` or\n `::1`, so they do not match the entries above. The practical exposure is\n correspondingly narrower.\n\nAn operator who verifies their own deployment can confirm the issue by inspecting the generated `pg_hba.conf` on a database node for the entries above.\n\n### Impact\n\nAn unprivileged local operating-system account on an affected database host obtains full control of every Postgres database on that host: read of all data, modification or destruction of all data, and any action available to a Postgres superuser. Under the systemd orchestrator this converts any local account into a database superuser with no additional prerequisites.\n\n### Affected versions\n\npgEdge Control Plane v0.1.0 through v0.10.1, inclusive.\n\n### Patches\n\nFixed in **v0.11.0**. Generated `pg_hba.conf` files no longer contain `trust` entries, and operator-supplied local authentication rules take effect. Upgrading to v0.11.0 or later is the recommended and, on v0.9.0 and later, the only complete remedy.\n\n### Workarounds\n\nThe available mitigation differs by version, and no mitigation is complete on current releases.\n\n**v0.1.0 – v0.8.1.** An operator could take the authentication files out of Patroni's control entirely: copy the generated `pg_hba.conf` and `pg_ident.conf`, edit the copies, and point the `hba_file` and `ident_file` settings at them through node-level `postgresql_conf`. This is effective but must be repeated per instance, including for every node added afterwards.\n\n**v0.9.0 – v0.10.1.** The above no longer applies. API validation rejects the `hba_file` and `ident_file` settings, and entries supplied through the `pg_hba_conf` specification array are appended below the hard-coded block rather than overriding it, so they do not take effect for local or loopback connections. The only partial mitigation available is to restrict the Unix socket: set `unix_socket_permissions` to `0700`, or to `0770` with the intended accounts placed in the `postgres` group. **This closes the socket path only. No supported configuration closes the loopback path on these versions.** Operators on v0.9.0 – v0.10.1 should upgrade to v0.11.0.","affected":[{"package":{"name":"github.com/pgEdge/control-plane","ecosystem":"Go","purl":"pkg:golang/github.com/pgEdge/control-plane"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.11.0"}]}],"database_specific":{"last_known_affected_version_range":"<= 0.10.1","source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-vq9p-w6wv-cr25/GHSA-vq9p-w6wv-cr25.json"}}],"references":[{"type":"WEB","url":"https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-125323"},{"type":"WEB","url":"https://github.com/pgEdge/control-plane/pull/470"},{"type":"WEB","url":"https://github.com/pgEdge/contLine truncated
|
||||
@@ -0,0 +1 @@
|
||||
{"schema_version":"1.9.2","id":"GHSA-w437-9mwm-j6vq","published":"2026-11-12T19:42:07Z","modified":"2026-11-12T19:45:03.186145298Z","aliases":["CVE-2026-125325"],"summary":"pgEdge RAG Server shared keyword index leaked results between concurrent unauthenticated requests","details":"### Impact\n\nDocuments belonging to one caller could be returned to another. Where an application passes a customer or tenant identifier as a search filter, that scoping could be defeated by ordinary concurrent traffic. **No injection and no malformed input are required** — normal load is enough.\n\nThe BM25 keyword index was a single per-pipeline object shared by every request. A request cleared it, refilled it from its own filtered corpus and then searched it, taking a separate lock for each step rather than holding the sequence as a unit. Concurrent requests therefore interleaved, and a search could run against a corpus that a different request's filter had populated.\n\n**Who is affected:** any deployment of pgEdge RAG Server at `1.0.0` or earlier, including all alpha and beta pre-releases, that serves concurrent queries — most acutely those relying on a search filter to separate tenants or customers. The query endpoint is unauthenticated in the affected versions (`internal/server/middleware.go:37` applies logging, panic recovery and optional CORS only), so both the party whose results leak and the party receiving them are anonymous remote callers.\n\n### Patches\n\n**Fixed in `2.0.0`. Upgrade to `2.0.0` or later.**\n\nThe index is now built per request rather than shared. The regression is pinned by `TestSearch_ConcurrentRequestsDoNotShareKeywordIndex` in `internal/pipeline/orchestrator_test.go`.\n\n**Upgrading does not tell a developer whether or not their application affected, and needs action beyond upgrading.** If a consuminag application scopes results by tenant, treat responses served under concurrent load on any affected version as potentially having included another tenant's documents. **Affected responses cannot be identified from the server's own logs**, so there is no retrospective check available.\n\n### Workarounds\n\nSet `hybrid_enabled: false` on the pipeline, which skips the keyword arm and with it the shared index. Callers can also pass `disable_hybrid` per request, which can only ever turn the arm off.\n\nNeither is a substitute for upgrading.","affected":[{"package":{"name":"github.com/pgEdge/pgedge-rag-server","ecosystem":"Go","purl":"pkg:golang/github.com/pgEdge/pgedge-rag-server"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260729020411-a09d4872356b"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-w437-9mwm-j6vq/GHSA-w437-9mwm-j6vq.json"}}],"references":[{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/security/advisories/GHSA-w437-9mwm-j6vq"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-125325"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/pull/44"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/commit/a09d4872356b510c81f11591845445c33ff45a84"},{"type":"PACKAGE","url":"https://github.com/pgEdge/pgedge-rag-server"},{"type":"WEB","url":"https://github.com/pgEdge/pgedge-rag-server/releases/tag/v2.0.0"}],"database_specific":{"cwe_ids":["CWE-362","CWE-488"],"github_reviewed":true,"github_reviewed_at":"2026-11-12T19:42:07Z","nvd_published_at":"2026-11-10T18:17:33Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"}]}
|
||||
@@ -1 +1 @@
|
||||
{"schema_version":"1.9.0","id":"GHSA-w6c6-c85g-mmv6","published":"2026-04-08T00:15:44Z","modified":"2026-09-10T03:51:03.642188195Z","aliases":["BIT-cosign-2026-39395","CVE-2026-39395","GO-2026-5694"],"summary":"Cosign's verify-blob-attestation reports false positive when payload parsing fails","details":"## Description\n\n`cosign verify-blob-attestation` may erroneously report a \"Verified OK\" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely.\n\n## Impact\n\nWhen `cosign verify-blob-attestation` is used without `--check-claims` set to `true`, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on `--type <predicate type>` to reject attestations with mismatched types would be lead to trust the unexpected attestation type.\n\n## Patches\n\nv3.0.6, v2.6.3\n\n## Workarounds\n\nAlways set `--check-claims=true` for attestation verification.","affected":[{"package":{"name":"github.com/sigstore/cosign","ecosystem":"Go","purl":"pkg:golang/github.com/sigstore/cosign"},"ranges":[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w6c6-c85g-mmv6/GHSA-w6c6-c85g-mmv6.json"}},{"package":{"name":"github.com/sigstore/cosign","ecosystem":"Go","purl":"pkg:golang/github.com/sigstore/cosign"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.6.3"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w6c6-c85g-mmv6/GHSA-w6c6-c85g-mmv6.json"}}],"references":[{"type":"WEB","url":"https://github.com/sigstore/cosign/security/advisories/GHSA-w6c6-c85g-mmv6"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-39395"},{"type":"PACKAGE","url":"https://github.com/sigstore/cosign"}],"database_specific":{"cwe_ids":["CWE-754"],"github_reviewed":true,"github_reviewed_at":"2026-04-08T00:15:44Z","nvd_published_at":"2026-04-07T20:16:33Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N"}]}
|
||||
{"schema_version":"1.9.2","id":"GHSA-w6c6-c85g-mmv6","published":"2026-04-08T00:15:44Z","modified":"2026-11-12T18:30:04.016897487Z","aliases":["BIT-cosign-2026-39395","CVE-2026-39395","GO-2026-5694"],"summary":"Cosign's verify-blob-attestation reports false positive when payload parsing fails","details":"## Description\n\n`cosign verify-blob-attestation` may erroneously report a \"Verified OK\" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely.\n\n## Impact\n\nWhen `cosign verify-blob-attestation` is used without `--check-claims` set to `true`, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on `--type <predicate type>` to reject attestations with mismatched types would be lead to trust the unexpected attestation type.\n\n## Patches\n\nv3.0.6, v2.6.3\n\n## Workarounds\n\nAlways set `--check-claims=true` for attestation verification.","affected":[{"package":{"name":"github.com/sigstore/cosign/v3","ecosystem":"Go","purl":"pkg:golang/github.com/sigstore/cosign/v3"},"ranges":[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w6c6-c85g-mmv6/GHSA-w6c6-c85g-mmv6.json"}},{"package":{"name":"github.com/sigstore/cosign/v2","ecosystem":"Go","purl":"pkg:golang/github.com/sigstore/cosign/v2"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.6.3"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w6c6-c85g-mmv6/GHSA-w6c6-c85g-mmv6.json"}},{"package":{"name":"github.com/sigstore/cosign","ecosystem":"Go","purl":"pkg:golang/github.com/sigstore/cosign"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.13.6"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-w6c6-c85g-mmv6/GHSA-w6c6-c85g-mmv6.json"}}],"references":[{"type":"WEB","url":"https://github.com/sigstore/cosign/security/advisories/GHSA-w6c6-c85g-mmv6"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-39395"},{"type":"WEB","url":"https://github.com/sigstore/cosign/pull/4801"},{"type":"WEB","url":"https://github.com/sigstore/cosign/commit/f1ad3ee952313be5d74a49d67ba0aa8d0d5e351f"},{"type":"PACKAGE","url":"https://github.com/sigstore/cosign"},{"type":"WEB","url":"https://github.com/sigstore/cosign/releases/tag/v2.6.3"},{"type":"WEB","url":"https://github.com/sigstore/cosign/releases/tag/v3.0.6"}],"database_specific":{"cwe_ids":["CWE-754"],"github_reviewed":true,"github_reviewed_at":"2026-04-08T00:15:44Z","nvd_published_at":"2026-04-07T20:16:33Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N"}]}
|
||||
Reference in new issue
Block a user