{"metadata": {"vulnerability": "CVE-2026-41161", "count": 13, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 8}, "linked_omitted": 0}, "data": [{"timestamp": "2026-04-15T18:57:50Z", "date_only": false, "value": "2026-04-15T18:57:50Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-04-17T16:34:45.524Z", "date_only": false, "value": "2026-04-17T16:34:45.524Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-41161", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-05-08T13:00:54.485Z", "date_only": false, "value": "2026-05-08T13:00:54.485Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-41161", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-05-08T13:00:54.485Z", "date_only": false, "value": "2026-05-08T13:00:54.485Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / GitHub_M", "record": "CVE-2026-41161", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-05-08T14:16:33Z", "date_only": false, "value": "2026-05-08T14:16:33Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-05-08T14:16:33.093Z", "date_only": false, "value": "2026-05-08T14:16:33.093", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-41161", "record": "FKIE_CVE-2026-41161", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-05-11T18:23:52.865Z", "date_only": false, "value": "2026-05-11T18:23:52.865549Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-41161", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2026-05-11T18:23:52.865Z", "date_only": false, "value": "2026-05-11T18:23:52.865549Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-41161", "record": "FKIE_CVE-2026-41161", "field": "metrics.ssvcV203.0.ssvcData.timestamp", "linked_record": true}, {"timestamp": "2026-05-11T18:24:40.217Z", "date_only": false, "value": "2026-05-11T18:24:40.217Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-41161", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-05-11T18:24:40.217Z", "date_only": false, "value": "2026-05-11T18:24:40.217Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2026-41161", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2026-05-12T13:31:20Z", "date_only": false, "value": "2026-05-12T13:31:20Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "modified", "linked_record": true}, {"timestamp": "2026-10-26T19:10:00.163Z", "date_only": false, "value": "2026-10-26T19:10:00.163", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-41161", "record": "FKIE_CVE-2026-41161", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-05T13:58:05Z", "date_only": false, "value": "2026-11-05T13:58:05.000000Z", "kind": "sighting", "label": "Seen", "source": "https://gist.github.com/arro-coder/0987b74b50357f37ed1f0e337a5e1b97", "record": "CVE-2026-41161", "field": "creation_timestamp", "uuid": "69f5d474-a7fc-4c5e-8cee-1bfcd2e6f93b", "content": "# Security Advisory: Username Enumeration via Timing Discrepancy in Sonatype Nexus Repository (LDAP/AD Realm)\n\n| | |\n|---|---|\n| **Product** | Sonatype Nexus Repository |\n| **Vendor** | Sonatype, Inc. |\n| **Affected version** | 3.91.1-04 |\n| **Tested version** | 3.91.1-04 (other versions not tested; likely also affected) |\n| **Fixed version** | None at time of publication |\n| **Affected configuration** | LDAP / Active Directory realm enabled |\n| **Vulnerability type** | CWE-208: Observable Timing Discrepancy |\n| **CVSS 3.1** | 5.3 (Medium) \u2013 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N` |\n| **CVE ID** | Requested (pending) |\n| **Found** | 2026-05 |\n| **Researcher** | Arnd Hautermans, netsharqs GmbH |\n\n## Summary\n\nThe authentication endpoint of Sonatype Nexus Repository responds measurably slower to login attempts for usernames that exist in a connected LDAP/Active Directory directory than to attempts for non-existent usernames. An unauthenticated remote attacker can use this timing difference to determine which directory usernames are valid.\n\nLocal Nexus user accounts (default security realm) are not affected.\n\n## Am I affected?\n\nA Nexus instance is affected if, under **Administration \u2192 Security \u2192 Realms**, an **LDAP** or **Active Directory** realm is on the list of active realms. Instances that authenticate only against the local Nexus realm do not expose the behaviour described here.\n\n## Details\n\n- **Endpoint:** `POST /service/rapture/session`\n- **Authentication required:** No (endpoint is reachable pre-authentication)\n- **Request body:** `username=&amp;password=` (`application/x-www-form-urlencoded`; both values Base64-encoded)\n- **Response for every attempt:** `HTTP 403` \u2014 the status code and body are identical for valid and invalid usernames; only the response time differs\n- **Observed response times:**\n  - Existing directory account, wrong password: approx. 45\u201370 ms\n  - Non-existent account: approx. 18\u201326 ms\n\nThe difference is most likely caused by the additional LDAP/AD bind and directory lookup that is only performed once a username is found in the directory, whereas requests for unknown usernames return early. Because the signal is a difference of means rather than a single reliable per-request value, the distinction is drawn statistically across repeated measurements rather than from a single request.\n\n## Proof of Concept\n\nThe behaviour was confirmed on an LDAP/AD-integrated Nexus instance. The measurement is realm-only and does not require valid credentials; any password value can be used, since every attempt returns `HTTP 403`.\n\n1. Collect a candidate list of usernames and a control list of random, non-existent usernames.\n2. For each candidate, send `POST /service/rapture/session` with the username in the Base64-encoded `username` field and an arbitrary Base64-encoded `password`, including the `X-Nexus-UI: true` header and a valid anti-CSRF token.\n3. Record the server response time for each request (for example via the response-timing column of an intercepting proxy, or the timing data of an HTTP client).\n4. To suppress network jitter, send each username repeatedly and compare the **median** response time per username rather than single values.\n5. Usernames whose median response time falls into the higher band (here \u2248 45\u201370 ms) correspond to accounts that exist in the directory; those in the lower band (\u2248 18\u201326 ms) do not.\n\nIn testing, more than 100 requests were issued, alternating between known-valid and known-invalid usernames. The two groups separated cleanly: every valid directory account fell into the higher timing band and every non-existent account into the lower band, while the HTTP status (`403`) and response body were identical across both groups.\n\n## Impact\n\nOn its own, the issue allows enumeration of valid directory accounts. Because the same endpoint was observed to have no brute-force protection (no lockout, no rate limiting, no CAPTCHA), an attacker can combine both weaknesses: first enumerate valid accounts, then run targeted password-guessing or password-spraying attacks against them. As the accounts are directory accounts, a successful guess may also give access to other systems that use the same directory.\n\n## Recommendations\n\n**For the vendor:**\n- Make the authentication path take the same time regardless of whether a username exists, e.g. by performing an equivalent dummy directory operation for unknown users.\n- Add built-in brute-force protection (rate limiting, progressive delays or temporary lockout) for the login endpoint.\n\n**For operators (until a fix is available):**\n- Put a reverse proxy in front of Nexus that rate-limits `/service/rapture/session`.\n- Restrict access to the Nexus UI and API to trusted networks.\n- Use SSO with MFA (e.g. SAML) instead of direct LDAP authentication where possible.\n- Enforce a strong password policy and lockout on the directory side.\n\n## Disclosure Timeline\n\n| Date | Event |\n|---|---|\n| 2026-05 | Vulnerability discovered during an authorized security assessment |\n| 2026-07 | Reported to Sonatype via HackerOne (report #3780151) |\n| 2026-07 | Report closed by the HackerOne triage team as \"Informative\"; clarification submitted, no further response |\n| 2026-07-31 | Follow-up sent to the Sonatype security team by email; only an automated reply received |\n| 2026-10-23 | CVE ID requested from Sonatype (CNA), deadline 2026-11-05; no response |\n| 2026-11-05 | CVE ID requested from MITRE CNA-LR |\n| 2026-11-05 | Public disclosure |\n\n## References\n\n- CWE-208: https://cwe.mitre.org/data/definitions/208.html\n- OWASP \u2013 Testing for Account Enumeration: https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\n- Comparable case (CWE-208, timing-based username enumeration): CVE-2026-40263\n- Comparable case (CWE-208, timing-based username enumeration): CVE-2026-41161\n", "url": "https://gist.github.com/arro-coder/0987b74b50357f37ed1f0e337a5e1b97"}], "metrics": {"as_of": "2026-11-20T02:11:36.113Z", "anchors": {"origin": {"timestamp": "2026-04-15T18:57:50Z", "date_only": false, "value": "2026-04-15T18:57:50Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-04-15T18:57:50Z", "date_only": false, "value": "2026-04-15T18:57:50Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 18861226.113842, "hours": 5239.229476067222, "days": 218.30122816946758, "min_seconds": 18861226.113842, "max_seconds": 18861226.113842, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-04-15T18:57:50Z", "date_only": false, "value": "2026-04-15T18:57:50Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-43FJ-QP3H-HRH5", "record": "GHSA-43FJ-QP3H-HRH5", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, "end": {"timestamp": "2026-11-20T02:11:36.113Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
